-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing no-refresh for exos_facts in Interfaces #517
Conversation
@Andersson007, hi! |
@plazukin hi, thanks for the PR!
cc @LindsayHill @ujwalkomarla @hlrichardson @rdvencioneck @JayalakshmiV @JayalakshmiV you are mentioned as maintainers of exos_ related stuff, so could you please take a look? |
Changelog fragment added! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@plazukin thanks for adding the fragment!
There's a small formatting thing to change.
As there are no integration tests, we cannot test it here.
Just be sure the no-refresh
is supported in older versions of the service. Please check their docs to check.
Not being a network engineer, I provide only general support for the collection like releasing, CI, etc.
Let's wait for someones feedback until next week. If there's no feedback, I'll merge the PR after Fosdem, i.e. at the end of the next week.
Thank you
- 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 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 | |
- exos_facts - returns 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 (https://github.com/ansible-collections/community.network/pull/517). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fixed it. Thank you
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool, thanks, so let's wait until the mid/end of the next week, then I'll merge if no objections
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, i hope that all fine.
Thank you :)
@Andersson007, hi! |
@plazukin hi, thanks for the reminder! busy time. Please do it in future PRs:) |
Backport to stable-5: 💚 backport PR created✅ Backport PR branch: Backported as #518 🤖 @patchback |
* 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)
* 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) Co-authored-by: Pavel Lazukin <45261138+plazukin@users.noreply.github.com>
@plazukin could you please take a look ^? |
@Andersson007, sorry i was on vacation |
@plazukin yep, you can use https://docs.ansible.com/ansible/devel/community/development_process.html#backporting-merged-prs-in-ansible-core (use |
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