Traffic control sets 1G mgmt network to 10G
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Invalid
|
Medium
|
Ran An |
Bug Description
Brief Description
-----------------
Traffic control sets mgmt to 10G when it is 1G for the actual link capacity as well as config controller ini file
Severity
--------
Major
Steps to Reproduce
------------------
1. Configure a system with 1G mgmt interface
mgmt interface in config.ini:
[LOGICAL_
LAG_INTERFACE = N
INTERFACE_MTU = 1500
INTERFACE_
INTERFACE_PORTS = eno2
[MGMT_NETWORK]
CIDR = 192.168.204.0/24
MULTICAST_
DYNAMIC_ALLOCATION = Y
LOGICAL_INTERFACE = LOGICAL_INTERFACE_1
[wrsroot@
1000
2. Check traffic control for mgmt network
[wrsroot@
class htb 1:40 parent 1:1 leaf 40: prio 4 rate 1Gbit ceil 10Gbit burst 15125b cburst 0b
class htb 1:10 parent 1:1 leaf 10: prio 3 rate 1Gbit ceil 10Gbit burst 15125b cburst 0b
class htb 1:1 root rate 10Gbit ceil 10Gbit burst 13750b cburst 0b
Expected Behavior
------------------
root rate and ceiling rate should be 1G instead of 10G
e.g.,
class htb 1:1 root rate 1000Mbit ceil 1000Mbit burst 15125b cburst 1375b
Actual Behavior
----------------
- class htb 1:1 root rate 10Gbit ceil 10Gbit burst 13750b cburst 0b
- Also in puppet log, cgcs_tc_setup.sh was setting it to 10G:
2018-10-
Reproducibility
---------------
Reproducible
System Configuration
-------
Any system with 1G mgmt interface and 2+ nodes.
Branch/Pull Time/Commit
-------
stx.18.10 as of "2018-10-
Timestamp/Logs
--------------
puppet.log:
2018-10-
summary: |
- STX: Traffic control sets 1G mgmt network to 10G + Traffic control sets 1G mgmt network to 10G |
tags: | added: stx.networking |
Changed in starlingx: | |
importance: | Undecided → Medium |
Changed in starlingx: | |
assignee: | Cindy Xie (xxie1) → Ran An (an.ran) |
Changed in starlingx: | |
status: | Triaged → Confirmed |
Changed in starlingx: | |
status: | In Progress → Invalid |
status: | Invalid → Opinion |
Changed in starlingx: | |
status: | Opinion → Confirmed |
tags: |
added: stx.2019.05 removed: stx.2019.03 |
tags: |
added: stx.2.0 removed: stx.2019.05 |
tags: | added: stx.retestneeded |
Targeting stx.2019.03 - this will have no impact unless the system is in an overload condition. It is also specific to a particular configuration (1G mgmt network). Therefore, it is not serious enough to block stx.2018.10