A patch strategy can make swact fail in a partially upgraded env
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Al Bailey |
Bug Description
Brief Description
-----------------
It was observed that the existence of a completed patch strategy on a controller running an older load, can prevent the swact to a controller that is being upgraded to a newer load.
This is due to the patch strategy attempting to be de-serialized in the newer load, which expects fields that do not exist and prevent the vim from starting.
Severity
--------
Minor
Steps to Reproduce
------------------
Install the previous load.
Run a patch orchestration to completion but do not delete it.
Upgrade the other controller
Attempt to swact to that controller
Expected Behavior
------------------
Should work
Actual Behavior
----------------
The vim fails to deserialize the completed patch strategy and causes the vim process to restart and fails the swact.
Reproducibility
---------------
Seen once, but the scenario to do this is reproducable
System Configuration
-------
Duplex
Branch/Pull Time/Commit
-------
The commit in the latest load that introduced this issue was merged on Mar 22, 2021
https:/
Last Pass
---------
N/A
Timestamp/Logs
--------------
The only important error log in the vim is
KeyError: 'retry_count'
Test Activity
-------------
Sanity
Workaround
----------
Delete the completed patch strategy on the older load before attempting to swact to the newer load.
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
tags: | added: stx.nfv |
Changed in starlingx: | |
importance: | Undecided → Low |
Fix proposed to branch: master /review. opendev. org/c/starlingx /nfv/+/ 790133
Review: https:/