-
Notifications
You must be signed in to change notification settings - Fork 559
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
some junos getters broken with junos-eznc 2.7.2 #2154
Comments
@amylieb Thanks for reporting this. |
We encountered the same issue. Thanks for reporting it @amylieb. We will consider your temporarily solution of downgrading junos-eznc. |
Same issue here. |
Someone want to fix it? |
Looks like someone saw this issue and created a corresponding one in the junos-eznc repo, with a potential fix slated for 2.7.3. If updating |
I saw similar issue/behavior when testing with napalm and ansible (i.e. that get_interfaces() was broken) and complaints pertaining to "is_up":
Reproduced with simple Python script outside of napalm-ansible. |
Temporary fix is to just downgrade to PyEZ 2.7.1. |
Description of Issue/Question
Did a fresh install of napalm into a venv and ran
get_interfaces
against a Juniper device. Got some weird output. Stripped down code for testing:Here is the resulting error:
I went into the source code for the Junos driver and added
print(dict(interfaces))
after line 472 to see what junos views gave me, here's what that looks like:This getter has worked just fine for me in the past, so the first thing I tried was to downgrade junos-eznc from 2.7.2 to 2.7.1 and everything works fine.
Because I was curious, I ran all the getters against my test device (An EX3400-48P running 20.4R3-S1.3) with junos-eznc at 2.7.2 and 2.7.1. Below are the ones that failed (by that I mean threw an exception) at 2.7.2 that did not at 2.7.1:
get_interfaces
get_network_instances
get_route_to
I glanced through the open issues on the pyEZ repo and didn't see anything obvious. I don't really have the time/interest to dig deep enough to open a detailed issue with them, but I want to give you guys a heads up about it - at the very least you can potentially update your requirements file.
The text was updated successfully, but these errors were encountered: