SX not boot up after host-unlock

Bug #1895307 reported by Peng Peng
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Invalid
Low
Peng Peng

Bug Description

Brief Description
-----------------
In SX, after host-unlock controller, host not boot up. System console log shows
"Give root password for maintenance"

Severity
--------
Major

Steps to Reproduce
------------------
host-unlock in SX

TC-name: system_monitoring/test_wr_analytics.py::test_wr_analytics[deploy_and_remove]

Expected Behavior
------------------
system boot up without issue

Actual Behavior
----------------
system did not boot up.

Reproducibility
---------------
Unknown - first time this is seen in sanity

System Configuration
--------------------
One node system

Lab-name: SM-3

Branch/Pull Time/Commit
-----------------------
2020-09-11_00-00-00

Last Pass
---------
2020-09-04_00-00-00

Timestamp/Logs
--------------
[2020-09-11 09:00:20,342] 314 DEBUG MainThread ssh.send :: Send 'system --os-username 'admin' --os-password 'Li69nux*' --os-project-name admin --os-auth-url http://[abcd:204::1]:5000/v3 --os-user-domain-name Default --os-project-domain-name Default --os-endpoint-type internalURL --os-region-name RegionOne host-unlock controller-0'
[2020-09-11 09:00:27,694] 436 DEBUG MainThread ssh.expect :: Output:
+-----------------------+--------------------------------------------+
| Property | Value |
+-----------------------+--------------------------------------------+
| action | none |
| administrative | locked |
| availability | online |

[2020-09-11 09:28:41,178] 314 DEBUG MainThread ssh.send :: Send '/usr/bin/ssh -o RSAAuthentication=no -o PubkeyAuthentication=no -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null sysadmin@2620:10a:a001:a103::81'
[2020-09-11 09:28:44,356] 436 DEBUG MainThread ssh.expect :: Output:
command-line line 0: Unsupported option "rsaauthentication"
ssh: connect to host 2620:10a:a001:a103::81 port 22: No route to host

console log:
Give root password for maintenance
(or press Control-D to continue):
sulogin: crypt failed: Invalid argument
Login incorrect

Give root password for maintenance
(or press Control-D to continue):

Test Activity
-------------
Sanity

Tags: stx.config
Revision history for this message
Peng Peng (ppeng) wrote :
tags: added: stx.retestneeded
Revision history for this message
Ghada Khalil (gkhalil) wrote :

@peng, Is this still an issue? Is it specific to the one lab referenced in the description?

Revision history for this message
Ghada Khalil (gkhalil) wrote :

Marking as stx.5.0 / medium priority - logs should be reviewed to determine what failed in the two cases above

Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
tags: added: stx.5.0 stx.config
tags: removed: stx.5.0 stx.config
Revision history for this message
Ghada Khalil (gkhalil) wrote :

Please ignore the comment above. It was added by mistake. Will wait for Peng to confirm if this was a one-off occurrence.

Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Medium → Undecided
Revision history for this message
Ghada Khalil (gkhalil) wrote :

This appears to have been an issue on this specific lab. It looks like a low level/BIOS issue; it doesn't seem related to the starlingx software. This particular lab is working now. Closing

Changed in starlingx:
importance: Undecided → Low
assignee: nobody → Peng Peng (ppeng)
status: Triaged → Invalid
Revision history for this message
Peng Peng (ppeng) wrote :

Not seeing this issue

tags: removed: stx.retestneeded
Ghada Khalil (gkhalil)
tags: added: stx.config
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.