Description of problem: Deploy multicluster hub fails to deploy with helm chart version mismatch error. (This is being deployed via operator hub with an iib index image) Version-Release number of selected component (if applicable): Index image - registry-proxy.engineering.redhat.com/rh-osbs/iib:11426 OCP: 4.6.0-0.nightly-2020-09-09-224210 Package manifest: - currentCSV: advanced-cluster-management.v2.0.2 How reproducible: 100% Steps to Reproduce: 1. Deploy OCP 4.6 2. Create catalog source using index image registry-proxy.engineering.redhat.com/rh-osbs/iib:11426 3. Deploy ACM via operatorhub 4. Deploy Multicluster hub instance via operatorhub Actual results: oc get subscriptions. cert-manager-sub -o yaml packages: charts-v1-cert-manager-3.6.0: lastUpdateTime: "2020-09-17T14:06:32Z" phase: Subscribed resourceStatus: conditions: - lastTransitionTime: "2020-09-17T14:05:32Z" status: "True" type: Initialized - lastTransitionTime: "2020-09-17T14:05:35Z" message: 'failed to install release: chart requires kubeVersion: >=1.11.0 which is incompatible with Kubernetes v1.19.0-rc.2+068702d' reason: InstallError status: "True" Expected results: Multicluster operator deploys succesfully Additional info:
Assigning to GRC for Gus Parvin to take a look
If you try this again with an OCP 4.6 build that is recent it will not have the issue. My OCP version: Server Version: 4.6.0-0.nightly-2020-09-28-125756 Kubernetes Version: v1.19.0+e465e66 I installed ACM 2.0.3 on top of this build without hitting the issue we had which was related to the kubernetes version in use by OCP. The pre-release kubernetes versions caused problems with some helm versioning that no longer happens with the released kubernetes versions.
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 (Red Hat Advanced Cluster Management for Kubernetes version 2.1 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:4954