Bootstrap replay is erroneously executing tasks when no config changes are made
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Rakshith M R |
Bug Description
Brief Description
-----------------
Bootstrap replay is erroneously executing tasks in situations where no configuration changes are made.
For instance, the tasks guarded by restart_tasks should only be executed given a reconfig (e.g., networking config change).
However, the flag is unexpectedly set and tasks such as Shut down and remove Kubernetes components are executed unnecessarily.
Upon investigation it is found that last_bootstrap_
Severity
--------
Major
Steps to Reproduce
------------------
Execute bootstrap replay ensuring no config changes:
1. Using subcloud: Run phase operation to run deploy bootstrap before running deploy config
or
2. Using System Controller: re-run ansible-bootstrap before unlock
Expected Behavior
-----------------
Bootstrap replay doesn't run Shut down and remove Kubernetes components
Actual Behavior
---------------
Bootstrap replay runs Shut down and remove Kubernetes components
Reproducibility
---------------
100% reproducible
System Configuration
-------
AIO-SX and DC
Test Activity
-------------
Developer Testing
Workaround
----------
N/A
Changed in starlingx: | |
assignee: | nobody → Rakshith M R (rakshith-mr) |
description: | updated |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.10.0 stx.config |
Fix proposed to branch: master /review. opendev. org/c/starlingx /ansible- playbooks/ +/924736
Review: https:/