starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Region has no field named 'nmame' #1047

New Issue
Closed
opened 2025-12-29 16:28:16 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:28:16 +01:00
Owner
Copy Link

Originally created by @beufanet on GitHub (Jun 19, 2017).

Issue type: FieldDoesNotExist after upgrading to v2.0

Python version: Python 2.7.9
NetBox version: Netbox 2.0.7

After upgrading from netbox 1.9.5 to 2.0.7, I tried to start using Regions features. And had the following error :

<class 'django.core.exceptions.FieldDoesNotExist'>

Region has no field named 'nmame'

Originally created by @beufanet on GitHub (Jun 19, 2017). ### Issue type: FieldDoesNotExist after upgrading to v2.0 **Python version:** Python 2.7.9 **NetBox version:** Netbox 2.0.7 After upgrading from netbox 1.9.5 to 2.0.7, I tried to start using Regions features. And had the following error : <class 'django.core.exceptions.FieldDoesNotExist'> Region has no field named 'nmame'
adam closed this issue 2025-12-29 16:28:16 +01:00
adam commented 2025-12-29 16:28:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 19, 2017):

Per the contributing guidelines, please provide the exact steps needed to recreate this behavior. Also, have you modified the code at all? The string "nmame" does not appear to be present anywhere in the code.

@jeremystretch commented on GitHub (Jun 19, 2017): Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md), please provide the exact steps needed to recreate this behavior. Also, have you modified the code at all? The string "nmame" does not appear to be present anywhere in the code.
adam commented 2025-12-29 16:28:17 +01:00
Author
Owner
Copy Link

@beufanet commented on GitHub (Jun 19, 2017):

You're right :( A bad substitution with vim on code. I will propose my change through push request.

Closed, sorry for the noise and one more time : thanks for the work !

@beufanet commented on GitHub (Jun 19, 2017): You're right :( A bad substitution with vim on code. I will propose my change through push request. Closed, sorry for the noise and one more time : thanks for the work !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1047
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?