Both controllers went for second reboot after DOR

Bug #1829288 reported by Nimalini Rasa on 2019-05-15
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Undecided
Unassigned

Bug Description

Brief Description
-----------------
After DOR (Dead Office Recovery), the both controllers went for second reboot.

Severity
--------
Provide the severity of the defect.
Major: System Recovered

Steps to Reproduce
------------------
2+10 system, launch 500 pods, power down all nodes, power up all nodes.

Expected Behavior
------------------
Expected the system to come up online and recover.

Actual Behavior
----------------
Both controller got rebooted after the first recovery.

Reproducibility
---------------
Reproducible

System Configuration
--------------------
2+10 system with 500 pods running

Branch/Pull Time/Commit
-----------------------
BUILD_DATE="2019-05-09"

Last Pass
---------
First time done.

Timestamp/Logs
--------------
Wed May 15 14:39:41 EDT 2019 : Power ON
Wed May 15 14:46:25 EDT 2019 login prompt
Wed May 15 14:48:13 EDT 2019 controller-0 went for reboot
Wed May 15 14:55:03 EDT 2019 kubrctl cmd worked
Wed May 15 14:55:13 EDT 2019 controller-1 went for reboot

Test Activity
-------------
Platform Testing

Nimalini Rasa (nrasa) wrote :
Numan Waheed (nwaheed) on 2019-05-17
tags: added: stx.retestneeded
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments