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

No change record created for interface when disconnecting a cable #17601

Closed
jeremystretch opened this issue Sep 25, 2024 · 0 comments · Fixed by #17603
Closed

No change record created for interface when disconnecting a cable #17601

jeremystretch opened this issue Sep 25, 2024 · 0 comments · Fixed by #17603
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@jeremystretch
Copy link
Member

Deployment Type

NetBox Cloud

NetBox Version

v4.1.1

Python Version

3.10

Steps to Reproduce

  1. Create two devices, A & B.
  2. Create interface 1 on device A and interfaces 1 and 2 on device B.
  3. Create a cable connecting interface 1 on both devices.
  4. Move the cable from device B interface 1 to interface 2.
  5. Inspect the change log.

Expected Behavior

Change records should be created for each of the following changes:

  • Delete the cable termination for interface 1
  • Creating the cable termination for interface 2
  • Nullifying the cable and cable_end fields on interface 1
  • Setting the cable and cable_end fields on interface 2

Observed Behavior

No change record is created for the cable and cable_end fields on interface 1.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Sep 25, 2024
@jeremystretch jeremystretch self-assigned this Sep 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant