starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Error fetching fields #5372

New Issue
Closed
opened 2025-12-29 19:27:15 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:27:15 +01:00
Owner
Copy Link

Originally created by @florianschendel on GitHub (Sep 16, 2021).

NetBox version

v3.0.2

Python version

3.9

Steps to Reproduce

More detailed description

  1. Install empty netbox
    I used simply the docker version with docker-compose

Netbox-docker

  1. login as admin create a user with the name flo

  2. create permissions for the new created user

image

  1. Login as user flo and create a new IP address
    It follows this message

image

Expected Behavior

Actually, we use only some models in Netbox like IPAM, Circuits and site/region information.
To all other models the users have no access (also no read access). Do not validate the fields with no access rights during website loading.

Observed Behavior

Error fetching fields

Originally created by @florianschendel on GitHub (Sep 16, 2021). ### NetBox version v3.0.2 ### Python version 3.9 ### Steps to Reproduce **More detailed description** 1. Install empty netbox I used simply the docker version with docker-compose [Netbox-docker](https://github.com/netbox-community/netbox-docker) 2. login as admin create a user with the name flo 3. create permissions for the new created user ![image](https://user-images.githubusercontent.com/33891080/136518762-d9d772e2-7fe3-4a74-ba2e-4c8557619cc3.png) 4. Login as user flo and create a new IP address It follows this message ![image](https://user-images.githubusercontent.com/33891080/136518877-5b5157ba-f742-4da4-b9d6-1faca726cd50.png) ### Expected Behavior Actually, we use only some models in Netbox like IPAM, Circuits and site/region information. To all other models the users have no access (also no read access). Do not validate the fields with no access rights during website loading. ### Observed Behavior Error fetching fields
adam added the type: bugstatus: revisions needed labels 2025-12-29 19:27:15 +01:00
adam closed this issue 2025-12-29 19:27:15 +01:00
adam commented 2025-12-29 19:27:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 16, 2021):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Sep 16, 2021): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:27:16 +01:00
Author
Owner
Copy Link

@florianschendel commented on GitHub (Sep 16, 2021):

Its difficult because my netbox is not a fresh/empty install ;)

Here my steps

  1. Create a new user in a fresh netbox installation with only rw access to the model IPAM
  2. All other models like DCIM/virtualization are blocked (no ro, no rw access)
  3. create an ip address

follow the instructions described in my last message

@florianschendel commented on GitHub (Sep 16, 2021): Its difficult because my netbox is not a fresh/empty install ;) Here my steps 1. Create a new user in a fresh netbox installation with only rw access to the model IPAM 2. All other models like DCIM/virtualization are blocked (no ro, no rw access) 3. create an ip address follow the instructions described in my last message
adam commented 2025-12-29 19:27:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 16, 2021):

You're going to need to provide much more detail than that. Take a few minutes to spell out exactly what you're doing at each step. Cite the specific attributes for each object you create, beginning with the user.

@jeremystretch commented on GitHub (Sep 16, 2021): You're going to need to provide much more detail than that. Take a few minutes to spell out _exactly_ what you're doing at each step. Cite the specific attributes for each object you create, beginning with the user.
adam commented 2025-12-29 19:27:16 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 27, 2021):

Closing as there has been no further response.

@jeremystretch commented on GitHub (Sep 27, 2021): Closing as there has been no further response.
adam commented 2025-12-29 19:27:16 +01:00
Author
Owner
Copy Link

@florianschendel commented on GitHub (Oct 8, 2021):

Closing as there has been no further response.

Hi, I updated the this case with the same information as in #7413

@florianschendel commented on GitHub (Oct 8, 2021): > Closing as there has been no further response. Hi, I updated the this case with the same information as in #7413
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: revisions needed type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5372
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?