SX controller take too long to recover after host-unlock
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Low
|
Al Bailey |
Bug Description
Brief Description
-----------------
30 minutes after SX host-unlock, controller node was still not recvoered.
Severity
--------
Major
Steps to Reproduce
------------------
SX host-unlock
TC-name: /networking/
Expected Behavior
------------------
controller node recovered less than 5 mins
Actual Behavior
----------------
controller node not recovered after 30 mins
Reproducibility
---------------
Unknown - first time this is seen in sanity
System Configuration
-------
One node system
Lab-name: SM-3
Branch/Pull Time/Commit
-------
2020-08-04_00-00-00
Last Pass
---------
2020-08-03_00-00-00
Timestamp/Logs
--------------
[2020-08-04 09:30:02,171] 314 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204:
[2020-08-04 09:58:21,003] 314 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204:
[2020-08-04 09:58:21,914] 436 DEBUG MainThread ssh.expect :: Output:
Authorization failed: Unable to establish connection to http://[abcd:204:
controller-0:~$
Test Activity
-------------
Sanity
Changed in starlingx: | |
importance: | Undecided → Low |
tags: | added: stx.metal |
tags: | added: stx.8.0 |
Changed in starlingx: | |
assignee: | nobody → Al Bailey (albailey1974) |
Log added at /files. starlingx. kube.cengn. ca/launchpad/ 1890323
https:/