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

Not able to create Child Devices #3953

Closed
abhilashchinthalapudi opened this issue Jan 17, 2020 · 0 comments
Closed

Not able to create Child Devices #3953

abhilashchinthalapudi opened this issue Jan 17, 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

@abhilashchinthalapudi
Copy link

abhilashchinthalapudi commented Jan 17, 2020

Environment

  • Python version: 3.6.8
  • NetBox version: 2.7.1

Steps to Reproduce

1.Choose Create a Device
2.Choose A Device Type which is a Child Device
3.Click Create
4.The exceptions appears if no Rack face was selected and if rack face was selected there is another exception which is what it supposed to be Child device types cannot be assigned to a rack face.

Other Issues I am seeing is We are able to update custom fields as well with the below exception
from pynetbox
The request failed with code 400 Bad Request: {'face': ['Child device types cannot be assigned to a rack face. This is an attribute of the parent device.']}

Step to reproduce:
device.custom_fields['Invoice Number'] = 1234
device.save()

Expected Behavior

Child Devices to be created
Custom Fields to be updated

Observed Behavior

Child Device Creation Failed
Custom Fields Value not updated with above exceptions

@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 17, 2020
@jeremystretch jeremystretch pinned this issue Jan 17, 2020
@jeremystretch jeremystretch unpinned this issue Jan 21, 2020
@lock lock bot locked as resolved and limited conversation to collaborators Apr 17, 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

No branches or pull requests

2 participants