AIO Plus system controller-1 failed after initial unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Bob Church |
Bug Description
Brief Description
-----------------
In AIO-DX plus system, After controller-1 was initially unlocked, controller-1 went to "failed" status.
Severity
--------
Major
Steps to Reproduce
------------------
during initial setup, After controller-0 is unlock/available.
unlock controller-1
Expected Behavior
------------------
controller-0 status unlock/available
Actual Behavior
----------------
controller-0 status unlock/failed
Reproducibility
---------------
Unknown - first time this is seen in sanity, will monitor
System Configuration
-------
Multi-node system
Lab-name: WP_8-12
Branch/Pull Time/Commit
-------
2020-03-23_20-00-00
Last Pass
---------
2020-03-22_16-04-38
Timestamp/Logs
--------------
[2020-03-24 05:50:49,028]
system host-list
+----+-
| id | hostname | personality | administrative | operational | availability |
+----+-
| 1 | controller-0 | controller | unlocked | enabled | available |
| 2 | compute-2 | worker | locked | disabled | online |
| 3 | controller-1 | controller | unlocked | disabled | failed |
| 4 | compute-1 | worker | locked | disabled | online |
| 5 | compute-0 | worker | locked | disabled | online |
+----+-
Test Activity
-------------
installation
tags: | added: stx.containers |
tags: | added: stx.4.0 |
Changed in starlingx: | |
importance: | Undecided → Medium |
tags: | added: stx.retestneeded |
log @ /files. starlingx. kube.cengn. ca/launchpad/ 1868728
https:/