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

Multiple interface edit error lead to lost device scope #7664

Closed
zombah opened this issue Oct 27, 2021 · 0 comments
Closed

Multiple interface edit error lead to lost device scope #7664

zombah opened this issue Oct 27, 2021 · 0 comments
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@zombah
Copy link

zombah commented Oct 27, 2021

NetBox version

v3.0.8

Python version

3.9

Steps to Reproduce

  1. Create device test-1, type f.e. Cisco ASR9901, at site xyz
  2. Create device test-2, type f.e. Juniper MX80, at site xyz
  3. Create interface LAG Bundle-Ether32 in device test-1 ints
  4. Create interface LAG ae32 in device test-2 ints
  5. Create interfaces Te0/0/0/[0-8] in device test-1 ints type SFP+
  6. Select multiple interface Te0/0/0/0,Te0/0/0/1, Te0/0/0/2 press edit multiple
  7. Choose Parent field and enter 32 there and press Apply for Error that only Virtual int apply for parent
  8. Choose Parent field and enter 32 - voila you can see ae32 also from test-2 device

Expected Behavior

Device scope persistent for multiple interface edit regarding of errors

Observed Behavior

Multiple int edit error intParent field lead to edit mode to loose device scope

@zombah zombah added the type: bug A confirmed report of unexpected behavior in the application label Oct 27, 2021
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Nov 2, 2021
@jeremystretch jeremystretch self-assigned this Nov 2, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants