controller unable to unlock after reinstall (inv_state stuck at reinstalling)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Eric MacDonald |
Bug Description
Brief Description
-------
Controller-1 was reinstalled successfully, however inv_state stuck at reinstalling, and unlock failed due to inv_stat was in stuck state.
Automation test logs http://
| install_output | text |
| install_state | completed |
| install_state_info | None |
| inv_state | reinstalling |
Unlock was failed with following error
raise exceptions.
E utils.exception
E Details: Can not unlock host controller-1 undergoing reinstall. Please ensure host has completed reinstall prior to unlock.
Steps to Reproduce
------------------
1.Install system with latest load.
2. lock Controller host
3. host reinstall
3. unlock controller
System Configuration
-------
Regular system AIO+DX + worker
Expected Behavior
------------------
Unlock success after reinstall.
Actual Behavior
----------------
As description says unlocked failure
Reproducibility
---------------
Seen only once in this lab.
Load
----
Build date 2020-08-07_20-00-00
Last Pass
---------
Timestamp/Logs
--------------
Reinstall command :
2020-08-
Unlock command :
2020-08-
Test Activity
-------------
Regression test
description: | updated |
description: | updated |
description: | updated |
tags: | added: stx.update |
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
tags: | removed: stx.retestneeded |
Please provide a timestamp for the reinstall step as well as the unlock step.
Also please update the reproducible comment as it doesn't seem to apply (ie no subcloud in this test)