IPv6 is not functional on management network in duplex-direct
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Teresa Ho |
Bug 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.
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
tags: | added: stx.networking |
description: | updated |
Changed in starlingx: | |
assignee: | Matt Peters (mpeters-wrs) → Teresa Ho (teresaho) |
Changed in starlingx: | |
status: | Triaged → In Progress |
Marking as stx.2.0 given the interest in IPv6 deployments. A duplex-direct configuration is popular as it removes the need for L2 switches to be configured for the mgmt/cluster networks.