| 2020-08-20 01:18:11 |
Kristine Bujold |
bug |
|
|
added bug |
| 2020-08-20 01:18:34 |
Kristine Bujold |
bug |
|
|
added subscriber John Kung |
| 2020-08-20 13:39:54 |
Kristine Bujold |
summary |
config: unnecessary re-apply of manifests on unlock |
config: unnecessary re-apply of manifests on unlock when using system modify --https_enabled |
|
| 2020-08-20 13:40:08 |
Kristine Bujold |
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' |
|
| 2020-08-20 13:45:22 |
Kristine Bujold |
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 '/opt/platform/config/20.06/.https_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem (in the case of this Jira we had an issue with tiller) the alarm is cleared.
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. |
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 '/opt/platform/config/20.06/.https_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem problems applying the manifests the alarm is cleared.
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. |
|
| 2020-08-20 13:46:11 |
Kristine Bujold |
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 '/opt/platform/config/20.06/.https_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem problems applying the manifests the alarm is cleared.
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. |
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_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem problems applying the manifests the alarm is cleared.
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. |
|
| 2020-08-20 13:50:20 |
Kristine Bujold |
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_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem problems applying the manifests the alarm is cleared.
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. |
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_config_required' gets set and never removed. If the user performs a lock/unlock on the lab, the conductor with run the _controller_config_active_apply() audit after the unlock. It will see the '.https_config_required' flag is set and raise the config alarm and apply the manifests. If there is no problem problems applying the manifests the alarm is cleared.
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. |
|
| 2020-08-24 17:55:21 |
Bill Zvonar |
tags |
|
stx.5.0 |
|
| 2020-08-24 17:55:44 |
Bill Zvonar |
starlingx: assignee |
|
John Kung (john-kung) |
|
| 2020-08-24 17:56:15 |
Bill Zvonar |
starlingx: status |
New |
Triaged |
|
| 2020-08-24 17:56:29 |
Bill Zvonar |
starlingx: importance |
Undecided |
Medium |
|
| 2020-08-26 01:29:20 |
Ghada Khalil |
tags |
stx.5.0 |
stx.5.0 stx.config |
|
| 2021-03-24 18:37:14 |
Bill Zvonar |
tags |
stx.5.0 stx.config |
stx.config |
|
| 2021-04-01 12:11:46 |
Ghada Khalil |
starlingx: importance |
Medium |
Low |
|
