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

The value of "primary ipv4" cannot be removed from a given VM in web UI #1553

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

Originally created by @mabazyar on GitHub (Feb 14, 2018).

Issue type

[ ] Feature request
[X ] Bug report
[ ] Documentation

Environment

  • Python version: 3.5.2
  • NetBox version: 2.2.9

Description

The primary-IPv4 value already assigned to a given VM can not be removed, but through the REST API.

Originally created by @mabazyar on GitHub (Feb 14, 2018). ### Issue type [ ] Feature request [X ] Bug report [ ] Documentation ### Environment * Python version: 3.5.2 * NetBox version: 2.2.9 ### Description The primary-IPv4 value already assigned to a given VM can not be removed, but through the REST API.
adam added the type: bugstatus: accepted labels 2025-12-29 16:32:54 +01:00
adam closed this issue 2025-12-29 16:32:54 +01:00
adam commented 2025-12-29 16:32:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 15, 2018):

Thank you for taking the time to report a bug. We'll need more information to investigate this issue. Per the contributing guidelines please ensure that you have included all of the following:

  • The environment in which NetBox is running
  • The exact steps that can be taken to reproduce the issue
  • Any error messages generated
  • Screenshots (if applicable)

Please update your issue to include all of the information listed above. If no response is received within a week, this issue will be closed. Thanks!

@jeremystretch commented on GitHub (Feb 15, 2018): Thank you for taking the time to report a bug. We'll need more information to investigate this issue. Per the [contributing guidelines](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md) please ensure that you have included all of the following: * The environment in which NetBox is running * The exact steps that can be taken to reproduce the issue * Any error messages generated * Screenshots (if applicable) Please update your issue to include all of the information listed above. If no response is received within a week, this issue will be closed. Thanks!
adam commented 2025-12-29 16:32:55 +01:00
Author
Owner
Copy Link

@mabazyar commented on GitHub (Feb 15, 2018):

Issue type

[ ] Feature request
[X ] Bug report
[ ] Documentation

Environment

Python version: 3.5.2
NetBox version: 2.2.9
OS: Centos 7

I have got a Netbox-2.2.9 instance installed on a Centos 7 supported by Python-3.5.2.

Description

  1. Create a new VM instance.
  2. Create an interface and get it attached to the VM.
  3. Assign a predefined IP address to the interface.
  4. Mark the IP address as "primary_ipv4" in the VM's entries.

In this case, there is no way to withdraw the "primary_ipv4" through web UI, and as a workaround, I did it by leveraging the relative API.
Like so:

curl -X PATCH -k --header 'Content-Type: application/json' -H "Authorization: Token 1234" -d '{"primary_ip4": null}' https://netbox.test.lan/api/virtualization/virtual-machines/8539/
@mabazyar commented on GitHub (Feb 15, 2018): ### Issue type [ ] Feature request [X ] Bug report [ ] Documentation ### Environment Python version: 3.5.2 NetBox version: 2.2.9 OS: Centos 7 I have got a Netbox-2.2.9 instance installed on a Centos 7 supported by Python-3.5.2. ### Description 1. Create a new VM instance. 2. Create an interface and get it attached to the VM. 3. Assign a predefined IP address to the interface. 4. Mark the IP address as "primary_ipv4" in the VM's entries. In this case, there is no way to withdraw the "primary_ipv4" through web UI, and as a workaround, I did it by leveraging the relative API. Like so: ``` curl -X PATCH -k --header 'Content-Type: application/json' -H "Authorization: Token 1234" -d '{"primary_ip4": null}' https://netbox.test.lan/api/virtualization/virtual-machines/8539/ ```
adam commented 2025-12-29 16:32:55 +01:00
Author
Owner
Copy Link

@mabazyar commented on GitHub (Feb 21, 2018):

Confirming the issue is fixed in v2.2.10.
Thanks @jeremystretch

@mabazyar commented on GitHub (Feb 21, 2018): Confirming the issue is fixed in v2.2.10. Thanks @jeremystretch
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 status: accepted type: bug
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#1553
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?