Installation failure if controller-0 unlocked with management on loopback interface
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Teresa Ho |
Bug Description
Brief Description
-----------------
When installing a standard (2+2) system with ansible, if controller-0 is unlocked while the management network is assigned to the loopback interface, the installation cannot be completed. No subsequent nodes can be brought up (since there is no management interface to pxeboot from) and the management network cannot be moved to a physical interface (since the controller cannot be locked).
Severity
--------
Major: controller-0 must be re-installed to recover
Steps to Reproduce
------------------
Install controller-0 (standard config) and unlock it before moving the management network to a physical interface.
Expected Behavior
------------------
The solution is probably to allow controller-0 to be locked in this specific case so the management network can be moved to a physical interface.
Actual Behavior
----------------
See above
Reproducibility
---------------
Reproducible
System Configuration
-------
Mult-node system
Branch/Pull Time/Commit
-------
SW_VERSION="19.01"
BUILD_TARGET=
BUILD_TYPE=
BUILD_ID="n/a"
JOB="n/a"
BUILD_BY="bwensley"
BUILD_NUMBER="n/a"
BUILD_HOST=
BUILD_DATE=
BUILD_DIR="/"
WRS_SRC_
WRS_GIT_
CGCS_SRC_
CGCS_GIT_
Last Pass
---------
Never
Timestamp/Logs
--------------
N/A
Test Activity
-------------
Developer Testing
Did you follow the instructions to update the mgmt interface?
system host-if-delete controller-0 lo
system host-if-modify -n mgmt -c platform --networks mgmt controller-0 eno2
system host-if-modify -m 9216 -n clusterhst -c platform --networks cluster-host controller-0 ens1f1
system host-if-modify -n oam -c platform --networks oam controller-0 eno1