Removing of a worker in stx does not reflect in Kubernetes

Bug #2046065 reported by OpenInfra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
New
Undecided
Unassigned

Bug Description

I removed a worker on the stx side but it the same node still listed in Kubernetes as NotReady.
Shouldn't the removal of workers in stx drop the node from k8s?

[sysadmin@controller-0 ~(keystone_admin)]$ kubectl get nodes
NAME STATUS ROLES AGE VERSION
controller-0 Ready control-plane,master 8d v1.23.1
controller-1 Ready control-plane,master 8d v1.23.1
worker-1 Ready <none> 8d v1.23.1
worker-12 Ready <none> 8d v1.23.1
worker-13 Ready <none> 8d v1.23.1
worker-2 Ready <none> 8d v1.23.1
worker-3 Ready <none> 8d v1.23.1
worker-4 Ready <none> 8d v1.23.1
worker-5 Ready <none> 8d v1.23.1
worker-6 Ready <none> 2d19h v1.23.1
worker-7 Ready <none> 2d2h v1.23.1
worker-8 Ready <none> 2d v1.23.1
worker-l40-01 NotReady <none> 13h v1.23.1
[sysadmin@controller-0 ~(keystone_admin)]$ system host-list
+----+---------------+-------------+----------------+-------------+--------------+
| id | hostname | personality | administrative | operational | availability |
+----+---------------+-------------+----------------+-------------+--------------+
| 1 | controller-0 | controller | unlocked | enabled | available |
| 6 | controller-1 | controller | unlocked | enabled | available |
| 7 | storage-0 | storage | unlocked | enabled | available |
| 8 | storage-1 | storage | unlocked | enabled | available |
| 13 | worker-12 | worker | unlocked | enabled | available |
| 14 | worker-13 | worker | unlocked | enabled | available |
| 15 | worker-2 | worker | unlocked | enabled | available |
| 16 | worker-3 | worker | unlocked | enabled | available |
| 18 | worker-5 | worker | unlocked | enabled | available |
| 23 | worker-4 | worker | unlocked | enabled | available |
| 24 | worker-1 | worker | unlocked | enabled | available |
| 25 | worker-6 | worker | unlocked | enabled | available |
| 27 | worker-7 | worker | unlocked | enabled | available |
| 29 | worker-8 | worker | unlocked | enabled | available |
| 35 | None | None | locked | disabled | offline |
| 37 | None | None | locked | disabled | offline |
+----+---------------+-------------+----------------+-------------+--------------+
[sysadmin@controller-0 ~(keystone_admin)]$ cat /etc/build.info
###
### StarlingX
### Release 22.06
###

OS="centos"
SW_VERSION="22.06"
BUILD_TARGET="Host Installer"
BUILD_TYPE="Formal"
BUILD_ID="r/stx.7.0"

JOB="STX_7.0_build_layer_flock"
<email address hidden>"
BUILD_NUMBER="18"
BUILD_HOST="starlingx_mirror"
BUILD_DATE="2022-08-30 13:10:20 +0000"

FLOCK_OS="centos"
FLOCK_JOB="STX_7.0_build_layer_flock"
<email address hidden>"
FLOCK_BUILD_NUMBER="18"
FLOCK_BUILD_HOST="starlingx_mirror"
FLOCK_BUILD_DATE="2022-08-30 13:10:20 +0000"

DISTRO_OS="centos"
DISTRO_JOB="STX_7.0_build_layer_distro"
<email address hidden>"
DISTRO_BUILD_NUMBER="3"
DISTRO_BUILD_HOST="starlingx_mirror"
DISTRO_BUILD_DATE="2022-07-28 14:23:47 +0000"

COMPILER_OS="centos"
COMPILER_JOB="STX_7.0_build_layer_compiler"
<email address hidden>"
COMPILER_BUILD_NUMBER="3"
COMPILER_BUILD_HOST="starlingx_mirror"
COMPILER_BUILD_DATE="2022-07-27 21:44:11 +0000"

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.