netbox-v3.2-beta1 - Cannot create new device bay on device or device-type #6168

Closed
opened 2025-12-29 19:37:39 +01:00 by adam · 4 comments
Owner

Originally created by @pobk on GitHub (Mar 3, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2-beta1

Python version

3.8

Steps to Reproduce

  1. Create a device type or use an existing
  2. Open "+Add component" -> "Device Bay"
  3. Fill in form. I used "iLO" for name and label and added some fluff in description.
  4. Click "Create"

Expected Behavior

I would expect a new device bay is created on the device or device-type and I'm redirected to the device-bays tab of the origin device/device-type.

Observed Behavior

You're redirected to the device tab, however, the device bay list is empty.

Originally created by @pobk on GitHub (Mar 3, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2-beta1 ### Python version 3.8 ### Steps to Reproduce 1. Create a device type or use an existing 2. Open "+Add component" -> "Device Bay" 3. Fill in form. I used "iLO" for name and label and added some fluff in description. 4. Click "Create" ### Expected Behavior I would expect a new device bay is created on the device or device-type and I'm redirected to the device-bays tab of the origin device/device-type. ### Observed Behavior You're redirected to the device tab, however, the device bay list is empty.
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:37:39 +01:00
adam closed this issue 2025-12-29 19:37:39 +01:00
Author
Owner

@pobk commented on GitHub (Mar 3, 2022):

This is reproducable on the demo-beta.netbox.dev instance.

@pobk commented on GitHub (Mar 3, 2022): This is reproducable on the demo-beta.netbox.dev instance.
Author
Owner

@jeremystretch commented on GitHub (Mar 3, 2022):

Thanks for the report! It looks like what's happening is that the component form validation is failing (likely because the chosen device type doesn't have the "parent" role to allow the assignment of device bays), but the view is redirecting the user as if the form submission was successful.

@jeremystretch commented on GitHub (Mar 3, 2022): Thanks for the report! It looks like what's happening is that the component form validation is failing (likely because the chosen device type doesn't have the "parent" role to allow the assignment of device bays), but the view is redirecting the user as if the form submission was successful.
Author
Owner

@pobk commented on GitHub (Mar 3, 2022):

Aha! Confirmed. I added 'parent' my test type and that works

@pobk commented on GitHub (Mar 3, 2022): Aha! Confirmed. I added 'parent' my test type and that works
Author
Owner

@jeremystretch commented on GitHub (Mar 3, 2022):

Fixed in 25dc9cc14a but I typo'd the commit message. 🤦

@jeremystretch commented on GitHub (Mar 3, 2022): Fixed in 25dc9cc14aca2caaa1119ec4c36112027c33e5b9 but I typo'd the commit message. :facepalm:
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6168