ansible bootstrap replay broken due to network range changes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
David Sullivan |
Bug Description
Brief Description
-----------------
ansible bootstrap replay fails to remove controller-0 ip from loopback interface
https:/
This is also hit during ansible replay here
./playbookconfi
Incorrectly assumes that floating ip is the second ip, and then controller-0 ip is the third, causing an error when it tries removing controller-0 ip from loopback interface, as it doesn't exist
Severity
--------
Provide the severity of the defect.
<Major: System/Feature is usable but degraded>
Steps to Reproduce
------------------
attempt to replay ansible bootstrap
Expected Behavior
------------------
ansible bootstrap replay should pass
Actual Behavior
----------------
ansible bootstrap replay fails. will pass on subsequent apply
System Configuration
-------
reproduced on ipv6 multinode, but should be reproducible on any
Changed in starlingx: | |
assignee: | nobody → David Sullivan (dsullivanwr) |
stx.3.0 / high priority - this issue was introduced by recent code changes