controller-0 fails to recover prior to configuration following bootstrap
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Won't Fix
|
Low
|
Tee Ngo |
Bug Description
Brief Description
-----------------
Rebooting the first controller following the ansible playbook apply, but prior to configuring and unlocking the host results in an unrecoverable system. The controller is missing critical configuration required for it to recover the local services.
Severity
--------
Major
Steps to Reproduce
------------------
1) Bootstrap the system using Ansible
2) Reboot Controller (sudo reboot)
Expected Behavior
------------------
The controller should be able to recover to the bootstrap state following the reboot. All host services should recover and should be ready to accept the required configuration to unlock it.
A reboot at this phase of the installation process may be required for patching of the system that would require a reboot of the host.
Actual Behavior
----------------
The controller services are in a failed state due to a partially applied puppet manifest and missing network configuration against the loopback interface.
Reproducibility
---------------
100% Reproducible
System Configuration
-------
All configurations.
Branch/Pull Time/Commit
-------
BUILD_ID=
Last Pass
---------
Never. It seems this scenario has never been tested.
Timestamp/Logs
--------------
From failed puppet apply:
2019-11-
2019-11-
2019-11-
2019-11-
2019-11-
2019-11-
2019-11-
Test Activity
-------------
Developer Testing - Patching
Recommending for stx.4.0 -- ansible config robustness item