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

Primary IP on Virtual Machine not sync with IPAM #7720

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

Originally created by @dwi2214 on GitHub (Mar 4, 2023).

NetBox version

v3.4.5

Python version

3.9

Steps to Reproduce

  1. Update primary ip4 on VM using api (via ipam.ip_addresses) --> Update successful
  2. Remove IP from IPAM via GUI to not assigned any VM --> Update successfull
  3. Check on VM, primary ip still exist using that IP

image

Expected Behavior

  • Sync between IPAM IPaddresses and Virtual Machine Primary IP

Observed Behavior

IP Address updated to not assigned to any VM, but VM still has assigned to that IP

Originally created by @dwi2214 on GitHub (Mar 4, 2023). ### NetBox version v3.4.5 ### Python version 3.9 ### Steps to Reproduce 1. Update primary ip4 on VM using api (via ipam.ip_addresses) --> Update successful 2. Remove IP from IPAM via GUI to not assigned any VM --> Update successfull 3. Check on VM, primary ip still exist using that IP ![image](https://user-images.githubusercontent.com/116805958/222878538-12a68d48-3dff-4b66-bfb1-f5a7a03e6bad.png) ### Expected Behavior - Sync between IPAM IPaddresses and Virtual Machine Primary IP ### Observed Behavior IP Address updated to not assigned to any VM, but VM still has assigned to that IP
adam added the type: bug label 2025-12-29 20:27:28 +01:00
adam closed this issue 2025-12-29 20:27:29 +01:00
adam commented 2025-12-29 20:27:29 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 4, 2023):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Mar 4, 2023): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 20:27:30 +01:00
Author
Owner
Copy Link

@drossy commented on GitHub (Mar 10, 2023):

I've just realised this looks similar to #11934 which I submitted a couple of days ago

@drossy commented on GitHub (Mar 10, 2023): I've just realised this looks similar to #11934 which I submitted a couple of days ago
adam commented 2025-12-29 20:27:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 10, 2023):

Okay. Would you like to close this issue, or extend the description above so that it can be treated as its own separate issue?

@jeremystretch commented on GitHub (Mar 10, 2023): Okay. Would you like to close this issue, or extend the description above so that it can be treated as its own separate issue?
adam commented 2025-12-29 20:27:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 16, 2023):

I'm going to close this in favor of #11934, which already has some discussion and a PR assigned to it.

@jeremystretch commented on GitHub (Mar 16, 2023): I'm going to close this in favor of #11934, which already has some discussion and a PR assigned to it.
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 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#7720
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?