-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Labels
severity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application
Milestone
Description
Deployment Type
Self-hosted
NetBox Version
v4.3.3 (also tested on 4.2.9)
Python Version
3.12
Steps to Reproduce
Deploy Netbox 4.3.3 with DEBUG enabled (statically in my case).
Go to System -> Configuration History page and add two configuration revisions.
Ensure config revision version #2 is active.
Execute 'manage.py --help'.
Reload Configuration History page and confirm current version reverted to #1.
Problem may be in core/apps.py line 45. Perhaps the clear.cache command needs to be gated in a similar manner as PR 14233 does for the (now defuct) manage.py clearcache command ?
I understand why clearing cache would be helpful in debug mode, but, the config_version variable seems like it should be an exception.
Expected Behavior
The configuration version should not be effected.
Observed Behavior
Configuration revision reverted to first version.
Metadata
Metadata
Assignees
Labels
severity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application