Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing device when editing IP address doesn't reset interface field #5617

Closed
Gelob opened this issue Jan 12, 2021 · 2 comments
Closed

Changing device when editing IP address doesn't reset interface field #5617

Gelob opened this issue Jan 12, 2021 · 2 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity

Comments

@Gelob
Copy link
Contributor

Gelob commented Jan 12, 2021

Environment

  • Python version: Python 3.6.8
  • NetBox version: 2.10.3

Steps to Reproduce

  1. Create two devices with the same interface names (may not be required)
  2. Assign an IP address to Device A
  3. Edit the IP address and under Interface Assignment change the Device it is assigned to Device B
  4. Click Update and get a Modified IP address modal but notice the assignment did not change to Device B.

Expected Behavior

I expected the IP address to now be assigned to Device B instead of A. However the interface field under Interface Assignment doesn't refresh/reset when I change the device so the assignment stayed with Device A.

Observed Behavior

The IP address assignment didn't change to Device B because the interface was still referencing device A

@DanSheps
Copy link
Member

Thank you for opening a bug report. It seems that the described functionality is intended behavior. If you meant to open a feature request instead, please close this issue and open a new one using the feature request template. Otherwise, please revise your post above to elaborate on why you believe the observed behavior is flawed.

@DanSheps DanSheps added the pending closure Requires immediate attention to avoid being closed for inactivity label Jan 13, 2021
@stale
Copy link

stale bot commented Jan 30, 2021

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale stale bot closed this as completed Jan 30, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pending closure Requires immediate attention to avoid being closed for inactivity
Projects
None yet
Development

No branches or pull requests

2 participants