Attempt to change a label key value that exists will update in kubernetes but not sysinv
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
David Sullivan |
Bug Description
Brief Description
-----------------
Attempt to change a label key value that already exists will update in kubernetes but silently fail in sysinv (resulting in setting discrepancies)
Severity
--------
standard
Steps to Reproduce
------------------
1. assign a label to a locked worker node
eg, add label "apps=enabled"
2019-10-
2019-10-
2. Check that the setting is added in kubernetes
Describe the node to see if the change is there
2019-10-
alternatively use the kubetcl get nodes command:
kubectl get nodes --show-labels
$ kubectl get node controller-0 --show-labels
NAME STATUS ROLES AGE VERSION LABELS
controller-0 Ready master 8h v1.16.2 apps=enabled,
Check that the label "apps" appears in the system inventory as "enabled"
$ system host-label-list controller-0
+------
| hostname | label key | label value |
+------
| controller-0 | apps | enabled
3. Now try to update the existing setting
$ system host-label-assign controller-0 apps=disabled
sysadmin@
Actual Behavior
--------------
The label updated in kubernetes but unexpectedly and silently failed to update in sysinv
$ kubectl get node controller-0 --show-labels
NAME STATUS ROLES AGE VERSION LABELS
controller-0 Ready master 8h v1.16.2 apps=disabled,
$ kubectl describe node controller-0 | grep apps=
Labels: apps=disabled
$ system host-label-list controller-0
+------
| hostname | label key | label value |
+------
| controller-0 | apps | enabled |
Expected Behavior
------------------
Expect that the label value should have updated to disabled in both kubernetes and system inventory
Reproducibility
---------------
Reproducible
System Configuration
-------
any
Branch/Pull Time/Commit
-------
2019-10-27_20-00-00
Timestamp
---------
see bash.log
2019-10-
see ERROR sysinv.
2019-10-28 14:57:35.580 426814 WARNING wsme.api [-] Client-side error: Avoiding lock action on already 'locked' host controller-0
2019-10-28 14:58:25.237 426814 INFO sysinv.
2019-10-28 14:58:25.262 425329 INFO sysinv.
2019-10-28 14:58:25.329 426814 ERROR sysinv.
2019-10-28 14:58:25.330 426814 INFO sysinv.
2019-10-28 14:58:25.332 426814 INFO sysinv.
Last Pass
--------------
Not passed
summary: |
- Attempt to change a key value that exists will update in kubernetes but - not sysinv + Attempt to change a label key value that exists will update in + kubernetes but not sysinv |
tags: | added: stx.retestneeded |
stx.3.0 / medium priority - discrepancy in label setting between k8s and sysinv