It has been observed that, on Standard systems, users are unable to
interact with containerized clients due to the fact that the `clients`
pods are being initialized without the `controller-` suffix in their
names. These names are relevant for the clients wrapper script to be
able to find and execute commands inside the clients containers [1].
The reason pods are being initialized with wrong names on Standard
systems is because the host-specific overrides are being generated for
hosts with `WORKER` personality instead of `CONTROLLER`, which makes no
sense as the containerized clients were designed to *only* run on
controller nodes.
Therefore, the proposed fix is straightforward and only requires us to
change the host personality required to generate host-specific
overrides.
Test Plan (on Standard):
PASS - Build python3-k8sapp-openstack package
PASS - Build stx-openstack-helm-fluxcd package
PASS - Build stx-openstack helm charts
PASS - Upload/apply stx-openstack
PASS - Source `/var/opt/openstack/admin-openrc` and check that the containerized clients are responding to commands as expected
PASS - Remove/delete stx-openstack
Reviewed: https:/ /review. opendev. org/c/starlingx /openstack- armada- app/+/892164 /opendev. org/starlingx/ openstack- armada- app/commit/ 44cc84b24b70c5a cb78f8ea37bd1d7 557eab0e18
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 44cc84b24b70c5a cb78f8ea37bd1d7 557eab0e18
Author: Luan Nunes Utimura <email address hidden>
Date: Mon Aug 21 13:26:53 2023 -0300
clients: Fix host-specific config overrides
It has been observed that, on Standard systems, users are unable to
interact with containerized clients due to the fact that the `clients`
pods are being initialized without the `controller-` suffix in their
names. These names are relevant for the clients wrapper script to be
able to find and execute commands inside the clients containers [1].
The reason pods are being initialized with wrong names on Standard
systems is because the host-specific overrides are being generated for
hosts with `WORKER` personality instead of `CONTROLLER`, which makes no
sense as the containerized clients were designed to *only* run on
controller nodes.
Therefore, the proposed fix is straightforward and only requires us to
change the host personality required to generate host-specific
overrides.
[1] https:/ /opendev. org/starlingx/ openstack- armada- app/src/ commit/ 4c238a8063c2781 5954c3aa151cdca e7dd5f67cb/ stx-openstack- helm-fluxcd/ stx-openstack- helm-fluxcd/ helm-charts/ clients/ templates/ bin/_clients- wrapper. sh.tpl# L52-L55
Test Plan (on Standard): k8sapp- openstack package helm-fluxcd package openstack/ admin-openrc` and check that the
containeriz ed clients are responding to commands as expected
PASS - Build python3-
PASS - Build stx-openstack-
PASS - Build stx-openstack helm charts
PASS - Upload/apply stx-openstack
PASS - Source `/var/opt/
PASS - Remove/delete stx-openstack
Closes-Bug: 2032382
Change-Id: I65b3fb64046567 d18abb5335042a3 df3b887d7c3
Signed-off-by: Luan Nunes Utimura <email address hidden>