config: swact failure reported by patch orchestration in DC subcloud
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
John Kung |
Bug Description
Brief Description
-----------------
Config out of date alarm prevents host-swact on multi node system. This blocked the
swact-hosts steps in DC orchestration
Severity
--------
Major: System/Feature is usable but degraded
Steps to Reproduce
------------------
Write down the steps to reproduce the issue
Expected Behavior
------------------
Write down what was expected after taking the steps written above
Actual Behavior
----------------
Patch orchestration was failed on DC_1 subcloud4 . This was due to swact failure further investigation showed swact was rejected as per below logs .
The swact is rejected because a runtime manifest (target 8c65766d-
sysinv 2020-12-22 14:43:59.570 108709 INFO sysinv.
sysinv 2020-12-22 14:43:59.571 108709 INFO sysinv.
sysinv 2020-12-22 14:43:59.609 108709 WARNING wsme.api [-] Client-side error: controller-0 target Config 8c65766d-
Reproducibility
---------------
Intermittent
System Configuration
-------
Multi-node system
Branch/Pull Time/Commit
-------
Branch and the time when code was pulled or git commit or cengn load info
2020-12-22
Last Pass
---------
Intermittent issue
Timestamp/Logs
--------------
sysinv 2020-12-22 14:43:59.570 108709 INFO sysinv.
sysinv 2020-12-22 14:43:59.571 108709 INFO sysinv.
sysinv 2020-12-22 14:43:59.609 108709 WARNING wsme.api [-] Client-side error: controller-0 target Config 8c65766d-
sysinv 2020-12-22 14:44:06.216 108709 INFO sysinv.
Test Activity
-------------
Feature Testing
Workaround
----------
Perform host-lock/
tags: | added: stx.ha |
Changed in starlingx: | |
status: | Triaged → In Progress |
stx.5.0 / medium - intermittent issue, resulting in orchestration failure