-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Aruba CX configuration pulled by NAPALM but not showing in Netbox UI #7041
Comments
Can you please provide a dump of the raw JSON being returned by the device so that someone without access to it can attempt to reproduce the bug? |
Hello, sorry for the delay, something got messed up with our infra and I wasn't able to retrieve the config.
|
@damien-martineau I was able to get a hold of an Aruba CX OVA to test with, and I can confirm that 14d87a3 fixes this. In a nutshell, NAPALM is returning an actual JSON object, not a raw string, so we needed to handle that accordingly. There's also some logic to recursively URL decode the response from NAPALM, as it seems either NAPLAM or the Aruba device is sending the data encoded (notice the keys like |
Thanks ! Do you think the patch will be available on 2.x ? |
NetBox version
v2.11.12
Python version
3.8
Steps to Reproduce
Expected Behavior
The running-config tab should return the configuration of the device as it does when doing the request through Netbox API with http://netbox.srv/api/dcim/devices/xxx/napalm/?method=get_config
Observed Behavior
The running config box only show
[object Object]
.Further testing showed the same behavior in Netbox v3.0-beta2.
(I'm not sure but I suspect the Javascript in the config tab template to not work properly with JSON formatted input.)
The text was updated successfully, but these errors were encountered: