Description of problem: ======================= When an AgentClusterInstall is changed, the related InfraEnv resource should reconcile. for example: if the user deletes and recreates the AgentClusterInstall resource, the backend cluster ID will change (essentially deregister and register a new backend cluster), and the InfraEnv image URL points to an an image that no longer exists. Version-Release number of selected component (if applicable): ============================================================= current git head 403985c8d95b5bef173a11326b3de7aec3fdef18 How reproducible: ================= 1/1 Steps to Reproduce: =================== 1. Create all resources to register a cluster and have an image for it: CD, ACI, ClusterImageSet, PullSecret, InfraEnv 2. Inspect the Image URL in InfraEnv 3. Delete and create ACI Actual results: =============== Image URL unchanged Expected results: ================= Image URL should change to point to the new backend cluster ID and image. Additional info: ================ SVC log from recreating ACI, note that InfraEnv does not reconcile: https://gist.github.com/nmagnezi/271ac9f1e4fdd0bd34253608ce6fdcfa InfraEnv currently watches for CD, which should stay (to catch changes in pullSecret). To optimize this, it can check if the pullSecret has changed in the CD and only reconcile in that case. All the other Relevant changes should be caught from within ACI.
How about instead of watching agent cluster install we can send event only when creating a cluster, this will reduce the generation events. In 4.9 when we will have streaming we can replace it to watch agent cluster install.
(In reply to Michael Filanov from comment #1) > How about instead of watching agent cluster install we can send event only > when creating a cluster, this will reduce the generation events. > In 4.9 when we will have streaming we can replace it to watch agent cluster > install. Yup. makes sense. will change the bug topic
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 (Moderate: OpenShift Container Platform 4.9.0 bug fix and security update), 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/RHSA-2021:3759