Duplex Upgrade failed on controller-0 after swacting

Bug #1978337 reported by Bo Yuan Chang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
High
Bo Yuan Chang

Bug Description

Brief Description
-----------------
When upgrading duplex subcloud, the process may fail after swacting active controller due to active alarm present.

Severity
--------
Provide the severity of the defect.
Major: System/Feature is usable but degraded

Steps to Reproduce
------------------
1. Upgrade system controller to N+1 load
2. Upgrade duplex subcloud to N+1 load

Expected Behavior
------------------
Subcloud successfully upgraded to N+1 load

Actual Behavior
----------------
creating VIM upgrade strategy: VIM strategy build failed: build-failed. Active alarms present ; 800.011, 800.001.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
Duplex subcloud

Branch/Pull Time/Commit
-----------------------
master

Last Pass
---------
not sure

Timestamp/Logs
--------------
N/A

Test Activity
-------------
Developer Testing

Workaround
----------
Delete the strategy, create a new strategy and apply again

Changed in starlingx:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Bo Yuan Chang (cby19961020)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to distcloud (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/distcloud/+/845376

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.opendev.org/c/starlingx/distcloud/+/845481

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on distcloud (master)

Change abandoned by "Bo Yuan Chang <email address hidden>" on branch: master
Review: https://review.opendev.org/c/starlingx/distcloud/+/845481
Reason: redundant submission

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to distcloud (master)

Reviewed: https://review.opendev.org/c/starlingx/distcloud/+/845376
Committed: https://opendev.org/starlingx/distcloud/commit/2805670668247eb4411c5a55191c0c6f578586cb
Submitter: "Zuul (22348)"
Branch: master

commit 2805670668247eb4411c5a55191c0c6f578586cb
Author: BoYuan Chang <email address hidden>
Date: Fri Jun 10 14:24:46 2022 -0400

    Raise orchestrated strategy post-swact wait time

    While upgrading a duplex subcloud, 'creating vim' step failed, due to
    the target host not being yet ready following a preceding swact.

    Increase waiting time following an orchestrated subcloud swact by one
    minute, to give more time for the subcloud to be ready for subsequent
    operations.

    Closes-Bug: 1978337

    Test Plan:

    1. Ensures Duplex subclouds can be upgraded from N to N+1 load
       without any failure

    Signed-off-by: BoYuan Chang <email address hidden>
    Change-Id: Icc115892290c4ddda3a4fe5f986764bc752a834f

Changed in starlingx:
status: In Progress → Fix Released
Ghada Khalil (gkhalil)
tags: added: stx.7.0 stx.distcloud
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.