Bug 1884142 - Changes to VM-Import CR's spec.infra field are ignored
Summary: Changes to VM-Import CR's spec.infra field are ignored
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Providers
Version: 2.5.0
Hardware: All
OS: All
high
high
Target Milestone: ---
: 2.5.0
Assignee: Piotr Kliczewski
QA Contact: Ilanit Stein
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-01 07:36 UTC by Nahshon Unna-Tsameret
Modified: 2020-11-17 13:25 UTC (History)
3 users (show)

Fixed In Version: hco-bundle-registry-container-v2.5.0-331
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-17 13:24:55 UTC
Target Upstream Version:
Embargoed:
pkliczew: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt hyperconverged-cluster-operator pull 859 0 None closed Bump VM_IMPORT to v0.2.3 2020-11-10 22:22:35 UTC
Github kubevirt hyperconverged-cluster-operator pull 861 0 None closed [release-1.2] Bump VM-Import to v0.2.3 (#859) 2020-11-10 22:22:35 UTC
Github kubevirt hyperconverged-cluster-operator pull 871 0 None closed Fix the reconciliation of components CRs 2020-11-10 22:22:35 UTC
Github kubevirt hyperconverged-cluster-operator pull 876 0 None closed [release-1.2] Fix the reconciliation of components CRs 2020-11-10 22:22:34 UTC
Github kubevirt vm-import-operator pull 413 0 None closed Update placement types 2020-11-10 22:22:35 UTC
Red Hat Product Errata RHEA-2020:5127 0 None None None 2020-11-17 13:25:06 UTC

Description Nahshon Unna-Tsameret 2020-10-01 07:36:43 UTC 
Description of problem:
When updating the spec.infra the VM-Import CR, there is no error, but also no change is done in the CR. The changes are ignored.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Deploy vm-import operator and CR
2. edit the spec.infra field in the CR, either directly, or by editing HCO CR
3. Read the VM-Import CR

Actual results:
No change, the field is still empty.


Expected results:
The changes are written to the CR.


Additional info:
Comment 1 Piotr Kliczewski 2020-10-01 07:46:02 UTC 
Nahshon, please provide more information about the issue. I do not understand what you mean you check vmimport CR. The placement should be applied to controller deployment.
Comment 5 Simone Tiraboschi 2020-10-08 15:50:28 UTC 
I fear we need also https://github.com/kubevirt/hyperconverged-cluster-operator/pull/871
Comment 7 Ilanit Stein 2020-11-11 07:02:02 UTC 
@Piotr,

Can you please add verification steps?
Comment 9 Piotr Kliczewski 2020-11-12 08:20:24 UTC 
Hahshon, I tried to update infra.nodeSelector for both HyperConverged and VMImportConfig but I see they get reconciled and the change is removed. Is there any recommended way to update spec.infra settings?
Comment 10 Piotr Kliczewski 2020-11-12 09:24:05 UTC 
After having offline conversation with Nahshon I see that it is working fine.
Comment 13 errata-xmlrpc 2020-11-17 13:24:55 UTC 
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 (OpenShift Virtualization 2.5.0 Images), 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:5127
Note You need to log in before you can comment on or make changes to this bug.