Kailas Vitthalrao Surkar 50ccc0830c Seed legacy thin multus images on System Controller for subcloud upgrades
A combined Platform & Kubernetes upgrade of an N-1 (STX-12) or N-2
(STX-11) subcloud deploys thin multus and requests
ghcr.io/k8snetworkplumbingwg/multus-cni:v4.2.x-debug from the System
Controller central registry during its networking upgrade step.

STX-13 deploys the StarlingX thick multus image
(docker.io/starlingx/multus-cni:stx.13.0-v1.0.0) and does not reference
the legacy upstream -debug tags in any system-images.yml. As a result
those tags are never seeded into the System Controller central registry,
and the subcloud image download fails with 404 manifest unknown.

The N-1/N-2 enabler patches intentionally retain thin multus on the
Bullseye from-side (the thin->thick migration is Trixie-only), so the
subclouds legitimately require these -debug tags; the gap is that the
System Controller does not host them.

Seed the legacy thin multus-cni images into the central registry on the
System Controller during kube image download. Scoped to the system
controller via distributed_cloud_role; the thick multus image deployed
by STX-13 at runtime is unchanged.

Test Plan:
PASS: build-pkgs -c -p sysinv
PASS: Platform upgrade of the central cloud from STX-11 to STX-13,
      followed by k8s upgrade from v1.32.13 to v1.35.2, then verify
      the required multus image is present in the central registry
PASS: Install STX-11 subcloud and perform a combined Platform &
      Kubernetes upgrade to STX-13 (k8s v1.32.13 to v1.35.2), verify
      the multus image download from the central registry succeeds
PASS: Standalone AIO-SX k8s upgrade, verify legacy multus images are
      not seeded

Closes-Bug: 2170357
Change-Id: I66b62e235b39d997c3ce70a5fae531f5ac767474
Signed-off-by: Kailas Vitthalrao Surkar <KailasVitthalrao.Surkar@windriver.com>
2026-10-14 05:07:10 -04:00
2026-07-16 07:14:46 -04:00
2019-04-19 19:52:42 +00:00
2018-05-31 07:35:52 -07:00
2023-07-19 12:18:04 -03:00

config

The starlingx/config repository handles the StarlingX configuration management services.

Its key component is the System Inventory Service (Sysinv), which provides the system command-line interface (CLI)1.

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/cli_ref/system.html↩︎

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

S
Description
StarlingX System Configuration Management
Readme Apache-2.0
124 MiB
2 Watchers 0 Forks
Languages
Python 98.2%
Shell 1.4%
CSS 0.2%