VIM orchestrator raises alarm on failing to remove the node taint.

Bug #2048908 reported by Vanathi Selvaraju
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
In Progress
Undecided
Unassigned

Bug Description

Brief Description
-----------------
Alarm 100.122 is raised by VIM orchestrator on failing to remove
node taint.

Steps to Reproduce
------------------
In a duplex system,
Lock in-active controller
system host-lock controller-1

Unlock controller-1
system host-unlock controller-1

Expected Behavior
------------------
'Services=disabled:NoExecute' taint to be removed from controller-1
There is no alarm 100.122 on the system.

Actual Behavior
----------------
'Services=disabled:NoExecute' taint remains in controller-1

Reproducibility
---------------
Seen once

System Configuration
--------------------
Duplex system (AIO-DX)

Timestamp/Logs
--------------
2023-10-18T20:09:49.619 controller-1 VIM_Infrastructure-Worker-0_Thread[109262] INFO kubernetes_client.py.130 Removing services:NoExecute taint from node worker-0

Taints present in the system /var/extra/containerization_kube.info

Name: worker-0
Roles: <none>
Labels: beta.kubernetes.io/arch=amd64
                    beta.kubernetes.io/os=linux
                    install=sco
                    kubernetes.io/arch=amd64
                    kubernetes.io/hostname=worker-0
                    kubernetes.io/os=linux
Taints: services=disabled:NoExecute
Unschedulable: false

Test Activity
-------------
system testing

Changed in starlingx:
status: New → In Progress
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.