Script error after update to NetBox 3.2.2
See original GitHub issueHi,
after updating to NetBox 3.2.2 I receive this error:
AttributeError: 'NoneType' object has no attribute '__name__'
Here is the complete error message
Do you have an idea, where this error comes from?
Edit: The current development and stable versions of netbox-sync work without any issue on NetBox 3.2.1
Issue Analytics
- State:
- Created a year ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Issues with upgrading from 3.1.1 to 3.2.0 #9255 - GitHub
I have been trying to upgrade our netbox server from version 3.1.1 to ... get the upgrade script to complete without any errors,...
Read more >Python ImportError after update to NetBox 2.11.3
Hi, I've just upgraded to NetBox 2.11.3 from NetBox 2.11.2 on a couple of VMs running on Oracle Linux 8 with Python 3.8....
Read more >Netbox upgrade is failing - Reddit
I ran upgrade.sh and when it got to the migrations part, things went all downhill from there. Here is the error message I...
Read more >NetBox v3.2: Custom Object Fields - YouTube
A quick look at the new object and multi-object custom field types in NetBox v3.2.
Read more >T296452 Upgrade Netbox to 3.2 - Wikimedia Phabricator
Upgrade -next to 3.1, . (Through a step on 2.11.12); Prepare changes to fix automation, reports, scripts, etc; Backup prod data (CSV dumps,...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi, yes please. Usually helps to understand the issue better.
You can find my mail address here: https://github.com/bb-Ricardo/netbox-sync/blob/d0143119de99fd40e39e923fe111045a85796b96/netbox-sync.py#L30
Thank you.
This issue has been fixed