DC: Subcloud upgrade fails in activating state due to application applied timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Yuxing |
Bug Description
Brief Description
-----------------
During the upgrade orchestration, the activation of a subcloud may fail due to a timeout in the process of uploading and applying applications.
Severity
--------
Major
Steps to Reproduce
------------------
Create an upgrade orchestration plan with two subclouds in parallel, apply it.
Expected Behavior
------------------
Upgrade succeeds
Actual Behavior
----------------
Upgrade fails in the step of activation
Reproducibility
---------------
Intermittent
System Configuration
-------
Distributed Cloud, Subcloud is AIOSX
Branch/Pull Time/Commit
-------
2020-06-27
Last Pass
---------
NA
Timestamp/Logs
--------------
sysinv 2020-09-01 03:05:57.175 101173 INFO controllerconfi
---
sysinv 2020-09-01 03:06:07.702 101173 ERROR sysinv.
--
sysinv 2020-09-01 03:14:15.569 101173 ERROR sysinv.
---
#######
platform.log
#######
2020-09-
2020-09-
2020-09-
Test Activity
-------------
Developer testing
Workaround
----------
Wait for all the previous application in "applied" or "uploaded" statute and activate the subcloud again
Changed in starlingx: | |
assignee: | nobody → Yuxing (yuxing) |
Changed in starlingx: | |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.5.0 stx.update |
description: | updated |
Changed in starlingx: | |
status: | In Progress → Fix Released |
https:/ /review. opendev. org/c/starlingx /config/ +/764780