starlingx/metal
Code Issues Proposed changes

Fix IPv6 resolution during Upgrade

Browse Source 
During an upgrade the controller.internal may not
be defined because the active controller is running
an old release, so the IPv6 DNS resolution fails
even if the scenario is IPv6.
An additional IPv6 DNS resolution to controller is
necessary to cover the upgrade scenario.

Tests done:

IPv6 AIO-SX fresh install
IPv6 AIO-DX fresh install
IPv4 AIO-DX upgrade from previous release
    without story 2010722 to new release
    that has the story 2010722 (not master)
IPv4 STANDARD upgrade from previous release
    without story 2010722 to new release
    that has the story 2010722 (not master)
IPv6 AIO-DX upgrade from previous release
    without story 2010722 to new release
    that has the story 2010722 (not master)
IPv6 DC lab upgrade from previous release
    without story 2010722 to new release
    that has the story 2010722 (not master)

Story: 2010722
Task: 49644

Depends-On: https://review.opendev.org/c/starlingx/config/+/909866

Change-Id: Ic4acc7432f351a65ba951d8ba8790b0ab90e32bc
Signed-off-by: Fabiano Correa Mercer <fabiano.correamercer@windriver.com>
This commit is contained in:
Fabiano Correa Mercer 2024-02-21 09:50:29 -03:00
parent 880df77a25
commit c6c308e982
1 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
kickstart/files/kickstart.cfg
View File

@ -2720,6 +2720,14 @@ else # vlan
# Check whether to use inet or inet6
ipv6_addr=$(dig +short AAAA controller.internal)
if [[ -z "${ipv6_addr}" ]]
then
# during an upgrade the controller.internal may not be defined
# but the scenario could be IPv6. So try to resolve the controller
ipv6_addr=$(dig +short AAAA controller)
fi
if [[ -n "${ipv6_addr}" ]]
then
boot_address_family=inet6