M2M_FIELD_TYPES undefined error with Netbox 2.3-develop #1416

Closed
opened 2025-12-29 16:32:05 +01:00 by adam · 3 comments
Owner

Originally created by @madkiss on GitHub (Nov 20, 2017).

[x] Bug report

Environment

  • Python version: 2.7.5
  • NetBox version: 2.3-develop

Description

We tried running develop-2.3 as we have use for the VLAN features added lately (not in production, so no worries). This seems to work great in general. We tried to add a VLAN interface to a machine, type "Other", on top of a bonding interface. When clicking the submit button, we see:

<class 'NameError'>
name 'M2M_FIELD_TYPES' is not defined

The interface is created nevertheless; but I am not sure if the correct entries are added to the database and also the error message should not appear.

Originally created by @madkiss on GitHub (Nov 20, 2017). [x] Bug report ### Environment * Python version: 2.7.5 * NetBox version: 2.3-develop ### Description We tried running develop-2.3 as we have use for the VLAN features added lately (not in production, so no worries). This seems to work great in general. We tried to add a VLAN interface to a machine, type "Other", on top of a bonding interface. When clicking the submit button, we see: <class 'NameError'> name 'M2M_FIELD_TYPES' is not defined The interface is created nevertheless; but I am not sure if the correct entries are added to the database and also the error message should not appear.
adam closed this issue 2025-12-29 16:32:05 +01:00
Author
Owner

@madkiss commented on GitHub (Nov 20, 2017):

I can confirm that the created VLAN entry is incorrect. It doesn't have any VLAN information attached to it.

@madkiss commented on GitHub (Nov 20, 2017): I can confirm that the created VLAN entry is incorrect. It doesn't have any VLAN information attached to it.
Author
Owner

@madkiss commented on GitHub (Nov 20, 2017):

I can also confirm that after creating the VLAN interface and seeind the error message, if I open the interface again and manually change the VLAN settings, it works and the proper VLAN is registered with the interface.

@madkiss commented on GitHub (Nov 20, 2017): I can also confirm that after creating the VLAN interface and seeind the error message, if I open the interface again and manually change the VLAN settings, it works and the proper VLAN is registered with the interface.
Author
Owner

@jeremystretch commented on GitHub (Dec 7, 2017):

Fixed in 859f891

@jeremystretch commented on GitHub (Dec 7, 2017): Fixed in 859f891
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1416