Patches are transferred and uploaded to the subclouds prematurely during patch orchestration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Bo Yuan Chang |
Bug Description
Brief Description
-----------------
Patches are uploaded and started in the subcloud before checking if the subcloud is patchable which prevents subsequent patch orchestration.
Severity
--------
Major
Steps to Reproduce
------------------
Start a patch orchestration while one or more subclouds have a management affecting alarm.
Expected Behavior
------------------
The orchestrated patching fails for the subcloud(s) with the management affecting alarm. However, there's no patching in progress alarm on the subcloud after the patch strategy is complete and removed.
Actual Behavior
----------------
Subclouds with the management affecting alarm end up with an additional alarm - the patching in progress alarm which is also management affecting which prevents subsequent patch orchestration on these subclouds.
Reproducibility
---------------
Readily reproducible.
System Configuration
-------
Distributed Cloud system
Branch/Pull Time/Commit
-------
December 12, 2021 master build
Last Pass
---------
Not sure if this test case has been covered before.
Timestamp/Logs
--------------
Issue is readily reproducible
Test Activity
-------------
Developer Testing
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Bo Yuan Chang (cby19961020) |
summary: |
- Add checker function for management affected alarm before patching on - subcloud + Patches are transferred and uploaded to the subclouds prematurely during + patch orchestration |
Gerrit review: https:/ /review. opendev. org/c/starlingx /distcloud/ +/823716 /opendev. org/starlingx/ distcloud/ commit/ e3a19ade738a151 ad3d0a1ed14ccfb a3ec6c55a8
Commit: https:/