Controller-0 did not become active after installation unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Paul-Ionut Vaduva |
Bug Description
Brief Description
-----------------
During fresh installation to unlock controller-0, controller-0 did not become active
Severity
--------
Major
Steps to Reproduce
------------------
DC installation
ssh to floating ip
source /etc/platform/
Expected Behavior
------------------
controller-0 is in active
Actual Behavior
----------------
controller-0 did not become active controller
Reproducibility
---------------
Not sure. Suspect it is intermittent, because we see installation and config passed on a different dc system with similar load.
System Configuration
-------
DC system
Lab-name: wp_18_21 (DC-3)
Branch/Pull Time/Commit
-------
2020-04-07_04-10-00
Last Pass
---------
Same system: 2020-04-05_04-10-00
DC-1: 2020-04-07_00-10-00
Timestamp/Logs
--------------
controller-0:~$ source /etc/platform/
Openstack Admin credentials can only be loaded from the active controller.
controller-0:~$ sudo sm-dump
Password:
/var/run/sm/sm.db not available.
Test Activity
-------------
installation
description: | updated |
description: | updated |
Changed in starlingx: | |
assignee: | Frank Miller (sensfan22) → Paul-Ionut Vaduva (pvaduva) |
tags: | added: stx.retestneeded |
log /files. starlingx. kube.cengn. ca/launchpad/ 1871638
https:/