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

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

Closed
pobk opened this issue Mar 3, 2022 · 4 comments
Closed
Assignees
Labels
beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@pobk
Copy link

pobk commented Mar 3, 2022

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.

@pobk pobk added the type: bug A confirmed report of unexpected behavior in the application label Mar 3, 2022
@pobk
Copy link
Author

pobk commented Mar 3, 2022

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

@jeremystretch jeremystretch added beta Concerns a bug/feature in a beta release status: accepted This issue has been accepted for implementation labels Mar 3, 2022
@jeremystretch jeremystretch self-assigned this Mar 3, 2022
@jeremystretch
Copy link
Member

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.

@pobk
Copy link
Author

pobk commented Mar 3, 2022

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

@jeremystretch
Copy link
Member

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

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
beta Concerns a bug/feature in a beta release 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