-
Notifications
You must be signed in to change notification settings - Fork 49
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
os10_facts throws exception #109
Comments
The "lxml exception" you are getting only on S5232F Switch or even on other switches also facing the same issue? |
possible can you share ansible.cfg file : |
ansible is installed locally with "pip" so I have no /etc/ansible/ansible.cfg and everything is default. I get the error on the other S5000 series switches as well. All I found so far is an issue with Py3 but Py2 is no longer supported by ansible. |
I think the problem is with some environmental issue or may be configuration. |
Any idea then where to start debugging? |
I tried to reproduce the issue on same platform (S5232F-ON & S5248F-ON) with same Image and same version of ansible, python and Collection. Find the enclosed details for the same: show version playbook:
ansible --version python3 --version ansible-galaxy collection list dellemc.os10 dellemc.os10 1.1.1 provided few lines of ansible execution log ansible-playbook -i inventory.yaml os10_ansible_facts_109.yaml PLAY [datacenter] ********************************************************************************************************************************************************************************************************************* TASK [dellemc.os10.os10_facts] ******************************************************************************************************************************************************************************************************** TASK [debug] **************************************************************************************************************************************************************************************************************************
} PLAY RECAP **************************************************************************************************************************************************************************************************************************** |
possible can we have live session to debug. |
nice idea but my time is running out today. I am back in office the January 5th. You may contact me over IRC (eJunky), I am currently hanging in #ansible-network channel. |
Starting all over again I managed to get things running with hard coded passwords. So my problem starts using "ssh_type=libssh" which I really want to use to utilize my ".ssh/config" and the corresponding private keys. Any ideas why this is happening? |
@prasadapr and @cultcom I just encountered this issue with the collection. I hit it because If you are using |
I have same problem and I changed the ssh connection to use paramiko at the hostvar level by using ansible_network_cli_ssh_type: paramiko , so other connections can use libssh that is better for reason mentioned. hostname: DSED101 |
@prasadapr This needs attention now that
|
Hi @lucastobey, @timway , @cultcom and @Eddgar0, Thanks for all your observations and comments. Will check and update on this. |
SUMMARY
I try to run os10_facts against a S5232F Switch and always get a lxml exception:
ISSUE TYPE
COMPONENT NAME
os10_facts
ANSIBLE VERSION
COLLECTION VERSION
CONFIGURATION
OS / ENVIRONMENT
STEPS TO REPRODUCE
EXPECTED RESULTS
I expect to get an dictionary with facts about the switch.
ACTUAL RESULTS
I get the exception as quoted above.
The text was updated successfully, but these errors were encountered: