StarlingX

  1. Bug #1836969
  2. Activity log

Activity log for bug #1836969

Date Who What changed Old value New value Message
2019-07-17 22:39:42 Ghada Khalil bug added bug
2019-07-17 22:39:57 Ghada Khalil bug added subscriber Matt Peters
2019-07-17 22:40:06 Ghada Khalil tags stx.networking
2019-07-17 22:42:51 Ghada Khalil description Brief Description ----------------- IPv6 is not functional when configured on the management interface on a duplex direct system. Because there is no carrier on the interface in the case of duplex-direct, dad can't complete, so the address stays in the tentative state, and cannot receive connections. That means that anything that tries connecting to the IPv6 mgmt address, including local services, will time out. Severity -------- Major - this precludes users from using IPv6 with duplex-direct configurations Steps to Reproduce ------------------ Configure a duplex-direct system with IPv6 Expected Behavior ------------------ This config should work Actual Behavior ---------------- This doesn't work. See explanation in the description. Reproducibility --------------- Reproducible System Configuration -------------------- Two node system connected as duplex-direct Branch/Pull Time/Commit ----------------------- Any stx load Last Pass --------- Never. This has always been broken. Timestamp/Logs -------------- Not required. Issue is reproducible. Test Activity ------------- Discussion with networking TL Brief Description ----------------- IPv6 is not functional when configured on the management interface on a duplex direct system. Because there is no carrier on the interface in the case of duplex-direct, DAD can't complete, so the address stays in the tentative state, and cannot receive connections. That means that anything that tries connecting to the IPv6 mgmt address, including local services, will time out. This will cause an issue with unlocking controller-0 once the interfaces are configured. Severity -------- Major - this precludes users from using IPv6 with duplex-direct configurations Steps to Reproduce ------------------ Configure a duplex-direct system with IPv6 Expected Behavior ------------------ This config should work Actual Behavior ---------------- This doesn't work. See explanation in the description. Reproducibility --------------- Reproducible System Configuration -------------------- Two node system connected as duplex-direct Branch/Pull Time/Commit ----------------------- Any stx load Last Pass --------- Never. This has always been broken. Timestamp/Logs -------------- Not required. Issue is reproducible. Test Activity ------------- Discussion with networking TL
2019-07-17 22:45:20 Ghada Khalil bug added subscriber Joseph Richard
2019-07-19 19:20:22 Ghada Khalil starlingx: importance Undecided High
2019-07-19 19:20:33 Ghada Khalil starlingx: status New Triaged
2019-07-19 19:20:45 Ghada Khalil tags stx.networking stx.2.0 stx.networking
2019-07-19 19:22:08 Ghada Khalil starlingx: assignee Matt Peters (mpeters-wrs)
2019-08-13 17:17:10 Ghada Khalil starlingx: assignee Matt Peters (mpeters-wrs) Teresa Ho (teresaho)
2019-08-14 14:37:43 Ghada Khalil starlingx: importance High Medium
2019-08-23 18:09:40 Ghada Khalil tags stx.2.0 stx.networking stx.3.0 stx.networking
2019-09-04 23:32:57 Ghada Khalil starlingx: status Triaged In Progress
2019-09-10 17:37:05 Bill Zvonar bug added subscriber Bill Zvonar
2019-09-19 17:23:26 OpenStack Infra starlingx: status In Progress Fix Released