IPAM can not change current ip address assignment when the ip is assigned to a virtual host #8337

Closed
opened 2025-12-29 20:35:29 +01:00 by adam · 2 comments
Owner

Originally created by @replior on GitHub (Jul 13, 2023).

NetBox version

v.3.5.5

Python version

3.8

Steps to Reproduce

Screenshot 2023-07-13 at 16 00 18

Can not remove current vm (which is not even shown in this view), or the interface as one can not click on the x

Expected Behavior

Earlier versions allowed deselecting vm and interface

Observed Behavior

nothing happens other than a "no parking" sign showing up at mouse over...

Originally created by @replior on GitHub (Jul 13, 2023). ### NetBox version v.3.5.5 ### Python version 3.8 ### Steps to Reproduce <img width="785" alt="Screenshot 2023-07-13 at 16 00 18" src="https://github.com/netbox-community/netbox/assets/139224912/50723975-0ae0-41a3-ab40-22952774ed34"> Can not remove current vm (which is not even shown in this view), or the interface as one can not click on the x ### Expected Behavior Earlier versions allowed deselecting vm and interface ### Observed Behavior nothing happens other than a "no parking" sign showing up at mouse over...
adam added the type: bugstatus: revisions needed labels 2025-12-29 20:35:29 +01:00
adam closed this issue 2025-12-29 20:35:29 +01:00
Author
Owner

@abhi1693 commented on GitHub (Jul 13, 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.

@abhi1693 commented on GitHub (Jul 13, 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.
Author
Owner

@jeremystretch commented on GitHub (Jul 20, 2023):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@jeremystretch commented on GitHub (Jul 20, 2023): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8337