Andre Kantek 77d1aaaf8e Select a valid management gateway
During IPv6 installation this script was generating an invalid mgmt_gw
value, due to an awk rule tuned for IPv4. This created an invalid
"gateway=1" in the ifupdown script, generating a parser error.

In a bonding setup with management as a vlan, the parsing error was
preventing the vlan interface over the ethernet port removal. The port
will be a slave on the bonding. Since the removal failed it cannot
add the vlan interface on top of the bonding interface.

The change uses the active controller floating value as a suitable
gateway, since at this stage the management network is the only
outside world option. If the value was not provided on API request
a valid IP is created (IPv4 or IPv6) to not generate parsing error.

For now there is no real case for the gateway to be used as all mgmt
traffic during kickstart and up to the first puppet manifest execution
is local, so in principle the gateway is just there for future use.
That is why it is not blocking installation.

Test Plan:
[PASS] Install AIO-DX (IPv4 and IPv6)
[PASS] Install Standard (IPv4 and IPv6)

Closes-Bug: 2070036

Change-Id: I4e76d878fecf589972bf93fdd75453a277c03d6a
Signed-off-by: Andre Kantek <andrefernandozanella.kantek@windriver.com>
2024-06-21 08:40:28 -03:00
2024-05-15 15:29:41 -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%