Description of problem: vmi is not responsive after label change Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. oc edit vmi xxx 2. change label "kubevirt.io/nodeName" value to some other valid value 3. save (wq) Actual results: virtctl console/start/stop not responsive Expected results: Move vmi to the new node? Additional info: It can be recovered after re-edit with the original value
This is probably virt.
As it stands right now, we need to block to edit the label. The reason the label is required is that we ca not watch by fields of CRs, that's why we have the label to find CRS for a given node. This is used by handler.
PR sent (upstream) https://github.com/kubevirt/kubevirt/pull/2136/ and is under review
https://www.google.com/url?q=https://github.com/kubevirt/kubevirt/pull/2136 is a workaround for this issue - users are no longer able to modify kubevirt internal labels.
verified on: oc version Client Version: v4.2.5 Server Version: 4.3.0-0.nightly-2019-12-19-050538 Kubernetes Version: v1.16.2 oc get csv -n openshift-cnv NAME DISPLAY VERSION REPLACES PHASE kubevirt-hyperconverged-operator.v2.2.0 Container-native virtualization Operator 2.2.0 kubevirt-hyperconverged-operator.v2.1.0 Succeeded following steps: 1. oc edit vmi xxx 2. change label "kubevirt.io/nodeName" value to some other valid value 3. save (wq) getting error message when trying to save.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:0307