cluster resize did not actually add new units for control plane

[Andre Ruiz]

I had a otherwise successful deployment of 2023.2/edge release 450, but I noticed that during the resize of the control plane it did not really add new units.

Initially it did:

14:25:55 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (23/25)
14:26:34 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (24/25)
14:29:25 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (25/25)
14:29:40 > Configure MySQL ...

Then added more nodes:

15:34:31 > Listing nodes in Sunbeam cluster ...
15:34:31 ┏━━━━━━━━━━━━━━━━━┳━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┓
15:34:31 ┃ Node ┃ Status ┃ Control ┃ Compute ┃ Storage ┃
15:34:31 ┡━━━━━━━━━━━━━━━━━╇━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━┩
15:34:31 │ ob76-node1.maas │ up │ x │ x │ x │
15:34:31 │ ob76-node2.maas │ up │ x │ x │ x │
15:34:31 │ ob76-node3.maas │ up │ x │ x │ x │
15:34:31 └─────────────────┴────────┴─────────┴─────────┴─────────┘

And then proceeded to resizing the control-plane over the 3 control nodes:

15:34:31 + sunbeam cluster resize
15:34:35 > Initializing Terraform from provider mirror ...
15:34:35 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... computing deployment sizing
15:34:38 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... deploying services
15:35:04 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (0/25)
15:35:26 > Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (25/25)
15:37:02 Resize complete.

As you can see, the number of services expected during the resize is the same as the initial deployment.

I did check in K8s underneath and indeed they are not there.

[Andre Ruiz (andre-ruiz)]

Logs for this build.

[Chris Johnston (cjohnston)]

Also seeing this on 2023.2 (481)

(2024.1/edge)