STD: In IPv6, after assigning a downed interface to the storage network, node fails on unlock because address remains in tentative

Bug #2030960 reported by Andre Kantek
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Low
Andre Kantek

Bug Description

Brief Description
-----------------

1. Configure the storage network - From GUI, System Configuration > Create Address Pool . Name: storage-pool, Network: 2001:DB8::/48

2.Create the storage network using the address pool:

{{ (keystone_admin)$ system addrpool-list | grep storage-pool | awk '{print$2}' | xargs system network-add storage-net storage true}}

3. Lock Controller-1 (Standby)

4. Check unassigned interfaces using command -

system host-if-list controller-1 -a

5.Create an interface using the address pool:

system host-if-modify -n storage0 -c platform --ipv6-mode static --ipv6-pool storage-pool controller-1 eno12409

system interface-network-assign controller-1 storage0 b9d42842-3e24-402c-8937-e8529db1f9fc

6. Unlock Controller

Severity
--------
Minor - corner case where the configured interface is not in an UP state

Reproducibility
----------------
100% Reproducible

System Configuration
---------------------
Standard in IPv6

Load info
---------
2023-08-04_18-00-08

Andre Kantek (akantek)
Changed in starlingx:
assignee: nobody → Andre Kantek (akantek)
Changed in starlingx:
status: New → In Progress
Ghada Khalil (gkhalil)
Changed in starlingx:
importance: Undecided → Low
tags: added: stx.9.0 stx.networking
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to stx-puppet (master)

Reviewed: https://review.opendev.org/c/starlingx/stx-puppet/+/890932
Committed: https://opendev.org/starlingx/stx-puppet/commit/7ec73cdfbe1ce7dc314b8c729f8bddadcc95a887
Submitter: "Zuul (22348)"
Branch: master

commit 7ec73cdfbe1ce7dc314b8c729f8bddadcc95a887
Author: Andre Kantek <email address hidden>
Date: Wed Aug 9 14:56:36 2023 -0300

    In IPv6 only search addresses in tentative if interface is UP

    During usage it was observed, in IPv6, that if a interface is with
    operational state in DOWN, it will take more time to leave the DAD
    state "tentative", if the system starts without carrier the flag
    remains until a carrier signal is provided.

    Since interfaces in DOWN are not affected by duplicated address
    in the network, this change adds a script to test this condition
    over active interfaces only.

    Test Plan:
    [PASS] remove the signal of an ethernet port that is configured and
            execute lock/unlock. Observe that there will be no puppet
            error in "wait-for-tentative".

    Closes-Bug: 2030960

    Change-Id: I8befd232324a2386879627f0d19ea7d14cccc126
    Signed-off-by: Andre Kantek <email address hidden>

Changed in starlingx:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.