-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Interface 32767 'Other' Type API bug #3967
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
Comments
This issue has been closed as it does not conform to one of the provided templates as required by the contributing guide. If you'd like to request that your issue be re-opened, please first update the content so that it matches the appropriate template (this may require rewriting your issue entirely). |
Sorry, I found this was discussed in mailing list. |
Could you let us know more specific steps to reproduce the issue like parameters of the interface? While I am trying api access to 'Other type' interface, cannot reproduce. |
I can reproduce this. On a system which has been updated from 2.6 to 2.7:
That value wasn't updated as part of the migration. I note that |
FYI: in the GUI at Checking in code: frontport and rearport never had the choice For completeness: I also checked console and power ports in the database. These are showing empty string as the value for |
Quick fix:
(but this ought to go into a new migration) |
For reference, original report was here. I wonder if it would also be worth making the line which raised the exception more robust, by changing |
The patch for this did not include interface templates. Re-opening so it can be re-addressed in the next release. |
Uh oh!
There was an error while loading. Please reload this page.
ment
Steps to Reproduce
https://netbox/api/dcim/interfaces/11373/
View API data of the interface
The text was updated successfully, but these errors were encountered: