Description of problem: Inventory changes are not reflected in CR status. For example: A plan with a critical condition for a VM already exists on the destination cluster will not be cleared when the problem is resolved by deleting the VM. This issue affects the following CRs: - Plan - NetworkMap - StorageMap - Host Version-Release number of selected component (if applicable): ALL. How reproducible: Always. Steps to Reproduce: 1. Create a Plan with a VM that already exists on the destination. 2. Note the CRITICAL condition. 3. Delete the VM on the destination. 4. Not the condition is not cleared. Actual results: Reconcile is not triggered and the condition is not cleared. Expected results: The change in the inventory should result in the CR being reconciled and the condition cleared. I don't think this need to be in real-time but perhaps within a minute is a reasonable expectation. Additional info:
https://github.com/konveyor/forklift-controller/pull/194 https://github.com/konveyor/forklift-controller/pull/204
This fix should be part of build v2.0.0-14, iib:64369.
Verified Plan Next: Verify the other CRS
Verified: Plan - as describe in the reproduction steps. Network - Create a NAD after networkmap is created and goes to NAD NotFound condition reason Storage - Create Storage Class after storagemap is created and goes to StorageClass NotFound condition reason Host - wip
@jortel @ I run the following scenario: 1. Created a host (UI) and allow it to become ready. 2. Put the host in maintenance mode. The Host remains in the same condition (and the migration fails, for obvious reason). cc: fdupont cc: istein
When watching inventory resources, each controller has a deliberately narrow set of changes it's interested in. For Host, it only triggers a Host CR reconcile when a referenced (vCenter) Host's path and/or name changes. We'd need to expand to include changes to: maintenance mode. However, we currently don't validate maintenance-mode in the back-end so the even if the Plan reconcile is triggered by the change in maintenance-mode, the Host CR will remain READY and the Plan will execute.
Host CR also verified. Closing this BZ, continue is : https://bugzilla.redhat.com/show_bug.cgi?id=1959306
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 (MTV 2.0.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-2021:2381
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days