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

Configuration Revision not showing data #16077

Closed
PieterL75 opened this issue May 10, 2024 · 2 comments · Fixed by #16082
Closed

Configuration Revision not showing data #16077

PieterL75 opened this issue May 10, 2024 · 2 comments · Fixed by #16082
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@PieterL75
Copy link
Contributor

Deployment Type

Self-hosted

NetBox Version

v4.0.0

Python Version

3.10

Steps to Reproduce

  1. Create a new Configuration Revision
  2. Save
  3. View that Configuration Revision (not edit)

Expected Behavior

All values of the fields are shown

Observed Behavior

The values are not visible
https://demo.netbox.dev/core/config-revisions/1/
image

@PieterL75 PieterL75 added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels May 10, 2024
@jeffgdotorg
Copy link
Collaborator

Thank you for reporting a suspected bug in NetBox. I have confirmed that this problem is reproducible on a fresh install of NetBox 4.0.1, so moving it out of triage state.

For future reference, please keep in mind that the demo system is not considered reliable for purposes of bug reporting as its state is ever in flux. Anybody can gain admin access to it and wreak arbitrary havoc, and its database gets reset nightly to offset this hazard.

@jeffgdotorg jeffgdotorg removed their assignment May 10, 2024
@jeffgdotorg jeffgdotorg added severity: medium Results in substantial degraded or broken functionality for specfic workflows status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation and removed status: needs triage This issue is awaiting triage by a maintainer labels May 10, 2024
@arthanson arthanson self-assigned this May 10, 2024
@arthanson arthanson removed the status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation label May 10, 2024
@PieterL75
Copy link
Contributor Author

@jeffgdotorg , thank you for reviewing.
I do find the issues on my one lab/qa instances, and i use the demo for ease of providing a link.
Works most of the time, when people don't break the demo.

@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows 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.

4 participants