-
Notifications
You must be signed in to change notification settings - Fork 23.7k
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
Cannot pull all facts with nxos_facts #18968
Comments
This issue has been originally posted in ansible//ansible-modules-core here. |
Some more information (as I think it is the same issue):
This playbook works totally fine:
But if I uncomment
|
The module documentation talks about a new timeout field which should be increased with NXAPI, especially when trying to gather all facts. Unfortunately, we cannot test that with the last devel version (2.3.0~git20170220.7bc7f1385) which cannot even establish a correct NXAPI connection with the target with exactly the same parameters as the ones used with 2.2.1.0-1:
|
Please confirm the fix and either close or update the issue |
Unfortunately, it's not solved with:
|
@privateip There's even an issue with your bot. |
@jean-christophe-manciot It was closed as the PR was merged. I've reopen it noe |
I was able to replicate the issue merged #21954 to fix it. All nxos_facts integration tests are now passing |
The issue is still there when trying to pull all facts with a
|
+1 I can confirm this is a problem as well when using the cli module on the current devel head. Additionally, it looks like the |
PR #22923 should fix up these issues |
@jean-christophe-manciot @wrouesnel the PR is merged, do you have time to take it for a spin and report on if the issue is resolved? |
I can test with an NX 9000 next week. |
@wrouesnel Thank would be great, thanks |
@privateip @gundalow @calfonso
On NX-OSv 7000 7.3(0)D1(1)
Same success on NX-OSv 9000 7.0(3)I5(1). As far as I'm concerned, this issue is solved. |
@jean-christophe-manciot Thank you for testing this. Will wait for final confirmation from @wrouesnel |
@wrouesnel Any feedback on this fix? |
Checking PR 21811, it looks like the module isn't working at all? My test playbook: ---
- hosts: tor-switches
connection: local
gather_facts: false
tasks:
- name: gather facts
nxos_facts:
gather_subset: all
host: #censored, an ip address#
username: will
ssh_keyfile: /home/will/.ssh/id_rsa
transport: cli
port: 22 Blows up with a traceback:
My ansible working dir:
|
Similarly with the current @devel HEAD:
|
@wrouesnel what is PR 21811? PR #22923 is the one that fixes nxos_facts although now its merged so you can run directly from I see the error in the second comment and will address shortly |
Apparently I'm an idiot and pulled entirely the wrong thing this morning, so ignore that first part. The second error is from |
@wrouesnel Have you tried with |
Our switches don't have the nxapi switched on at the moment. The module claims to support the |
@wrouesnel replicated and fixing it now ... should have a PR posted in the next hour or so |
Awesome. It'll be about 10 hours before I'm on the same network as our nx9ks again. |
PR has been merged into devel and will be part of the next 2.3 RC |
Fixed with the cli provider and Cisco 9k switch - thanks! |
@wrouesnel thanks for testing, closing the issue. |
ISSUE TYPE
COMPONENT NAME
nxos_facts
ANSIBLE VERSION
CONFIGURATION
inventory = ./hosts
gathering = explicit
roles_path = /home/actionmystique/Program-Files/Ubuntu/Ansible/git-Ansible/roles
private_role_vars = yes
log_path = /var/log/ansible.log
fact_caching = redis
fact_caching_timeout = 86400
retry_files_enabled = False
OS / ENVIRONMENT
SUMMARY
Running nxos_facts triggers a fatal error (connection timeout), whereas I can manually login into the target node with SSH or run nxos-feature on the same targets.
STEPS TO REPRODUCE
EXPECTED RESULTS
Successful nxos_facts
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: