Description of the problem: submariner-addon pods stuck in clbo with latest RHACM 2.4 ds snapshot. submariner-addon-54db489c78-lrgz2 1/1 Running 7 (5m10s ago) 83m Release version: Operator snapshot version: 2.4.0-DOWNSTREAM-2021-08-17-07-07-34 OCP version: 4.9.0-0.nightly-2021-08-16-082143 Env: Hub = ocp baremetal ipi, ipv4 connected (libvirt) Browser Info: N/A Steps to reproduce: 1. Deploy ocp baremetal ipi, ipv4 connected hub 2. Created catalogsource from 2.4.0-DOWNSTREAM-2021-08-17-07-07-34 3. Deploy RHACM on hub via catalogsource 4. Create mch cr Actual results: submariner-addon-54db489c78-lrgz2 1/1 Running 7 (5m10s ago) 83m Expected results: Pod starts without error Additional info: My deployment is having multiple pods get into clbo, but they look to be due to different issues, so opening individual bz's. submariner-addon-54db489c78-lrgz2 1/1 Running 6 (34s ago) 67m managedcluster-import-controller-v2-c7676fd74-csfsd 0/1 CrashLoopBackOff 14 (3m12s ago) 65m hive-operator-774646d57-dklrc 0/1 CrashLoopBackOff 16 (5m11s ago) 67m management-ingress-c8c5f-5499494b95-ks2m9 1/2 Running 22 (5m29s ago) 65m management-ingress-c8c5f-5499494b95-nprns 1/2 Running 22 (5m19s ago) 65m
a compatible issue of ACM and OCP 4.9. the v1beta1.CustomResourceDefinition is deprecated in OCP 4.9. need to upgrade CustomResourceDefinition to v1 in submariner-addon.
Verified working - All pods in a Running status on latest downstream snapshot OCP Hub: 4.9.0-0.nightly-2021-08-25-185404 Snapshot: 2.4.0-DOWNSTREAM-2021-08-25-19-01-28
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 (Important: Red Hat Advanced Cluster Management 2.4 images and security updates), 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:4618
Update QA contact for CLC