Patch orchestration stuck after service restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Yuxing |
Bug Description
Brief Description
-----------------
During a patch orchestration, after a restart of the
dcmanager-
etc.), the application of the on-going patch strategy on subclouds
will be unhealthy( e.g. progress stuck due to the missing of the green
threads, missing the cache of the RegionOne patches).
Severity
--------
Minor
Steps to Reproduce
------------------
1 Create and apply a patch orchestration
2 Manually restart the dcmanager-
Expected Behavior
------------------
The patch strategy should be in a stable status
Actual Behavior
----------------
The patch strategy stuck in applying, cannot delete
Reproducibility
---------------
Reproducible
System Configuration
-------
DC
Branch/Pull Time/Commit
-------
Jun 16th load
Last Pass
---------
na
Timestamp/Logs
--------------
na
Test Activity
-------------
Developer Testing
Workaround
----------
Editing the DB to fail the patch strategy.
Changed in starlingx: | |
assignee: | nobody → Yuxing (yuxing) |
summary: |
- Patch orchestration stuck after serivce restart + Patch orchestration stuck after service restart |
tags: | added: stx.distcloud |
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.7.0 |
Fix proposed to branch: master /review. opendev. org/c/starlingx /distcloud/ +/846447
Review: https:/