From c6c308e982c2addab1ab2e2e808a223b4aaa11c7 Mon Sep 17 00:00:00 2001 From: Fabiano Correa Mercer Date: Wed, 21 Feb 2024 09:50:29 -0300 Subject: [PATCH] Fix IPv6 resolution during Upgrade 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 --- kickstart/files/kickstart.cfg | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/kickstart/files/kickstart.cfg b/kickstart/files/kickstart.cfg index a8cb299c..028aaecc 100644 --- a/kickstart/files/kickstart.cfg +++ b/kickstart/files/kickstart.cfg @@ -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