Bootstrap replay is erroneously executing tasks when no config changes are made

Bug #2073885 reported by Rakshith M R
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
In Progress
Undecided
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_config.j2 template was not configured properly and there is a mismatch while comparing previous configuration values with current configurations.

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
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to ansible-playbooks (master)
Changed in starlingx:
status: New → In Progress
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.