Inactive controller stays in booting after mgmtnetwork down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
High
|
Eric MacDonald |
Bug Description
Title
-----
Inactive controller host stays in booting after management network is admin down
Brief Description
-----------------
After management network is down on Standby controller (unlocked/enabled) controller is rebooted and after that status keeps in 'booting' all the time (2hsr on the test), interface remains down all the time.
Severity
--------
Major
Steps to Reproduce
------------------
1. ssh to inactive (aka standby) controller host
2. disable management network (eno2)
$ sudo ifconfig eth1 down
3. Verify that controller start rebooting
4. Verify that controller rebooted and become active
Expected Behavior
------------------
controller rebooted and become active
Actual Behavior
----------------
controller remains in 'booting' for long time (at least 2hrs)
Reproducibility
---------------
100%
System Configuration
-------
AIO-DUPLEX Two node system redundant
Branch/Pull Time/Commit
-------
Branch: r-2018.10
Timestamp/Logs
--------------
Logs attached and controller output here http://
tags: | added: stx.2018.10 |
tags: | added: stx.metal |
Changed in starlingx: | |
assignee: | nobody → Eric MacDonald (rocksolidmtce) |
Changed in starlingx: | |
importance: | Undecided → High |
Changed in starlingx: | |
status: | New → Invalid |
tags: |
added: stx.1.0 removed: stx.2018.10 |
Issue can reproduce in Virtual Multinode Local Storage in all hosts.