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

Server Error when creating permission with constraints #15115

Closed
Kani999 opened this issue Feb 12, 2024 · 2 comments · Fixed by #15137
Closed

Server Error when creating permission with constraints #15115

Kani999 opened this issue Feb 12, 2024 · 2 comments · Fixed by #15137
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@Kani999
Copy link

Kani999 commented Feb 12, 2024

Deployment Type

Self-hosted

NetBox Version

v3.7.1

Python Version

3.10

Steps to Reproduce

  1. Add new Permission https://demo.netbox.dev/users/permissions/add/
  2. Setup Constraints as {"role": "server"}
  3. Create
  4. Obtain Server Error
<class 'ValueError'>

Field 'id' expected a number but got 'server'.

Python version: 3.8.10
NetBox version: 3.7.1
Plugins: 
  netbox_demo: 0.3.1

Expected Behavior

Server Error 500 should not be raised.
It should display some kind of validation popup.

Observed Behavior

Server Error occurs

<class 'ValueError'>

Field 'id' expected a number but got 'server'.

Python version: 3.8.10
NetBox version: 3.7.1
Plugins: 
  netbox_demo: 0.3.1
@Kani999 Kani999 added the type: bug A confirmed report of unexpected behavior in the application label Feb 12, 2024
@Kani999
Copy link
Author

Kani999 commented Feb 12, 2024

Recreated from #15017 because I cannot reopen the issue.
I suppose the problem still needs to be fixed.

@DanSheps DanSheps added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Feb 12, 2024
@DanSheps
Copy link
Member

See: #15019

@jeremystretch jeremystretch self-assigned this Feb 13, 2024
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Feb 13, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available 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.

3 participants