Fabiano Correa Mercer c6c308e982 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 <fabiano.correamercer@windriver.com>
2024-02-29 17:12:07 -03:00
2023-08-08 12:15:00 -03:00
2023-08-29 16:50:22 -04:00
2023-10-11 14:40:38 +00:00
2019-04-19 19:52:33 +00:00
2023-04-28 12:38:51 -04:00
2018-05-31 07:36:43 -07:00
2023-07-19 12:32:13 -03:00
2022-12-26 23:26:54 +00:00

metal

The starlingx/metal repository handles StarlingX Bare Metal Management1.

This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.

References


  1. https://docs.starlingx.io/api-ref/metal↩︎

  2. https://opendev.org/starlingx/manifest.git↩︎

Description
StarlingX Bare Metal and Node Management, Hardware Maintenance
Readme 15 MiB
Languages
C++ 83%
Shell 10.2%
Python 3.3%
C 2.5%
Makefile 1%