Skip to content

"'DeviceBayForm' has no field named 'installed_device'" when trying to edit device bay details with an installed device in it #3822

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

Closed
hoalex opened this issue Jan 2, 2020 · 0 comments
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@hoalex
Copy link

hoalex commented Jan 2, 2020

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.9

Steps to Reproduce

  1. Create Device Type "Parent" with Parent/child status = Parent and add one device bay "Bay 1"
  2. Create Device Type "Child" with Parent/child status = Child
  3. Create Devices "Parent" and "Child"
  4. Assign device "Child" to bay of device "Parent"
  5. Navigate to device "Parent" and select the "Edit device bay" icon for "Bay 1"
  6. Do not change anything in the form, simply click on "Update"

Error message appears:
2020-01-02 11_48_16-Server Error

Expected Behavior

No error message when trying to update the details of an installed device in a device bay.

Observed Behavior

Changing details of a device bay only seems to be possible as long as the device bay has a status of "Vacant". Once a device is installed in the device bay, the above error message appears.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application labels Jan 2, 2020
jeremystretch added a commit that referenced this issue Jan 2, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 2, 2020
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

Successfully merging a pull request may close this issue.

2 participants