[PR #517/ffdd7c28 backport][stable-5] Missing no-refresh for exos_facts in Interfaces #518
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![patchback[bot]](https://avatars.githubusercontent.com/in/21488?s=60&v=4){kind=small}
* missing no-refresh for exos_facts in Interfaces * exos_fixtures: rename show_port_config --------- Co-authored-by: Pavel Lazukin <plazukin@croc.ru> (cherry picked from commit ffdd7c2)
Andersson007
deleted the
patchback/backports/stable-5/ffdd7c2844c0e192d77653a95bcf5094d08fbf74/pr-517
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a backport of PR #517 as merged into main (ffdd7c2).
SUMMARY
Without the change exos_facts return timeout error when we use connection type network_cli.
It happened because we send command without 'no-refresh' and script cli2json.py stuck in loop while reading console output
ISSUE TYPE
COMPONENT NAME
exos: exos_facts
ADDITIONAL INFORMATION
You can reproduction of the problem with this task and 'ansible_connection: network_cli':
I use the component with EXOS 16.2.5.4, but also face a problem in EXOS 30.5.1.15