Andre Kantek f6c3afbf39 Only use defined addresses for certSANs configuration
A problem was identified during the migration from AIO-SX to AIO-DX
with dual-stack (IPv4 and IPv6). The Kubernetes certSANs configuration
failed when the primary OAM address pool was configured with the
addresses of controller0 and controller1. This failure stemmed from
the absence of a corresponding secondary OAM address pool
configuration for the same controllers. Consequently, an invalid
string was generated for the config map configuration.

This change tests the defined address variables before adding them to
the certsans string.

Test Plan
=========
[PASS] install AIO-SX in dual-stack:
       - migrate config to AIO-DX
       - adjust the addresses for both OAM pools
       - unlock controller-0
       - proceed with controller-1 installation
[PASS] install AIO-SX in single-stack and migrate to AIO-DX

Closes-Bug: 2103782

Change-Id: Id022ca86d14c0bb60d691b739e383a6e92c6ab54
Signed-off-by: Andre Kantek <andrefernandozanella.kantek@windriver.com>
2025-03-24 11:40:25 -03:00
2021-02-19 12:14:38 -06:00
2019-09-09 14:52:12 -05:00
2019-09-09 14:52:12 -05:00

stx-puppet

The starlingx/stx-puppet repository handles the Puppet service1.

The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.

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://www.puppet.com↩︎

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

Description
StarlingX Puppet modules and manifests
Readme 20 MiB
Languages
Puppet 58.9%
Python 21.4%
HTML 7.4%
Shell 7%
Ruby 4.7%
Other 0.6%