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.

Sign up for GitHub

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

Jump to bottom

Deleting an Interface with an assigned CircuitTermination deletes the CircuitTermination #1071

Closed
jeremystretch opened this issue Apr 12, 2017 · 0 comments
Closed

Deleting an Interface with an assigned CircuitTermination deletes the CircuitTermination #1071

jeremystretch opened this issue Apr 12, 2017 · 0 comments
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@jeremystretch
Copy link
Member

Issue type: Bug report

Python version: 2.7.6
NetBox version: 1.9.5

If a CircuitTermination is defined to bind a Circuit to an Interface, deleting that Interface will also delete the CircuitTermination (the Circuit will remain). We should change the on_delete behavior of this relationship from CASCADE to PROTECT.
@jeremystretch jeremystretch added the type: bug A confirmed report of unexpected behavior in the application label Apr 12, 2017
jeremystretch added a commit that referenced this issue Apr 20, 2017
@jeremystretch
Fixes #1071: Protect assigned circuit termination when an interface i…
95a97ed 
…s deleted
@jeremystretch jeremystretch mentioned this issue Apr 21, 2017
Merged
lampwins pushed a commit to lampwins/netbox that referenced this issue Oct 13, 2017
@jeremystretch
Fixes netbox-community#1071: Protect assigned circuit termination whe…
af7786a 
…n an interface is deleted
@lock lock bot locked as resolved and limited conversation to collaborators Jan 18, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeremystretch