config: unnecessary re-apply of manifests on unlock when using 'system modify --https_enabled'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
John Kung |
Bug Description
Brief Description
-----------------
Found a bug in sysinv where if the user issue the CLI command “system modify --https_enabled <true/false>” (which does not requires a lock/unlock to be applied), the config flag '.https_
A fix for this would be to have stx-puppet clear the flag as well after the changes are performed.
Severity
--------
Minor
Steps to Reproduce
------------------
- system modify --https_enabled <true/false>
- lock/unlock node
- Right after the unlock see 250.001 alarm 'Configuration is out-of-date' being raised and cleared
Expected Behavior
------------------
The alarm should have not been raised since there was no config changes
Actual Behavior
----------------
250.001 alarm 'Configuration is out-of-date' being raised and cleared
Reproducibility
---------------
Reproducible
System Configuration
-------
AIO-SX
Branch/Pull Time/Commit
-------
master
Last Pass
---------
Timestamp/Logs
--------------
Test Activity
-------------
Developer Testing
Workaround
----------
None. This is not service affecting other than an unnecessary alarm being raised and cleared.
summary: |
- config: unnecessary re-apply of manifests on unlock + config: unnecessary re-apply of manifests on unlock when using system + modify --https_enabled |
summary: |
- config: unnecessary re-apply of manifests on unlock when using system - modify --https_enabled + config: unnecessary re-apply of manifests on unlock when using 'system + modify --https_enabled' |
description: | updated |
description: | updated |
description: | updated |
tags: | added: stx.config |
Changed in starlingx: | |
importance: | Medium → Low |
Hi John, can you propose a solution.