AIO-SX not going enabled when oam interface is down
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Bin Qian |
Bug Description
SM requires at least 1 interface (oam, mgmt or infra) to be in "up" state before starting scheduling service, this is correct as SM needs to communicate to the peer to determine the role it is. This is not true for AIO-SX, as it is designed to not having peers, so it shouldn't wait for interface to be in "up" state.
This bug causes an AIO-SX not being enabled if oam interface is down.
Severity
--------
This is critical as it causes unexpected system out of service
Step to reporduce
--------
Configure an AIO-SX, unplug the oam cable and reboot the node. When the node is up, the node will not be enabled until the oam cable plug in.
Expected Behavior
--------
The system should be enabled, and an alarm should be raise for oam is down.
Reproducibility
--------
Reproducible
System configuration
--------
Single node system AIO-SX
Last pass
--------
Never
Test Activity
--------
Manual
tags: | added: stx.ha |
Changed in starlingx: | |
assignee: | nobody → Bin Qian (bqian20) |
importance: | Undecided → Medium |
status: | New → Triaged |
tags: | added: stx.3.0 |
Marking as stx.3.0 / medium priority - this issue prevents simplex systems from being properly configured in the oam interface is down.