Description of problem: Deploy of CNV 2.5 (Kustomize.sh) failing in a disconnected cluster Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Deploy disconnected OCP 4.6 cluster 2. Apply a disconnected IIB - named "rh-verified-operators" 2. Deploy CNV 2.5 - CNV_SOURCE=brew, CNV_VERSION=2.5 3. Actual results: Failed Expected results: Succeed Additional info: 20:28:10 ++ /root/cnv-qe.rhcloud.com/BM-cnvqe-cnvcl4/bin/oc get catsrc rh-verified-operators -n openshift-marketplace -o 'jsonpath={.metadata.name}' --ignore-not-found 20:28:21 + CAT_SRC=rh-verified-operators 20:28:21 + '[' -n rh-verified-operators ']' 20:28:21 ++ /root/cnv-qe.rhcloud.com/BM-cnvqe-cnvcl4/bin/oc get opsrc rh-verified-operators -n openshift-marketplace -o 'jsonpath={.metadata.name}' --ignore-not-found 20:28:21 error: the server doesn't have a resource type "opsrc" 20:28:21 + OP_SRC= 20:28:21 + rm -rf /tmp/tmp.S1Ep3plhXI
hi @Inbar, The issues @Asher raised were: 1. It can be determined if the cluster on which the script is running on, is disconnected or not, based on the value of the OperatorHub custom resource, and we don't want additional parameter for the script for that. 2. The subscription is pointing to a catalog source named "hco-catalogsource" which is dynamically created by the kustomize script. However, in a disconnected cluster, there is no such catalog source name. (the existing catalog sources are not being touched if the cluster is disconnected). I addressed these two topics here: https://gitlab.cee.redhat.com/contra/cnv-qe-automation/-/merge_requests/466 Note that I derived that names of the catalog sources according to the old appregistry namings: production --> redhat-operators osbs --> rh-osbs-operators stage --> redhat-operators-stage please confirm if that's correct for the disconnected clusters you are using. Thanks
(In reply to Oren Cohen from comment #6) > hi @Inbar, > > The issues @Asher raised were: > 1. It can be determined if the cluster on which the script is running on, is > disconnected or not, based on the value of the OperatorHub custom resource, > and we don't want additional parameter for the script for that. > 2. The subscription is pointing to a catalog source named > "hco-catalogsource" which is dynamically created by the kustomize script. > However, in a disconnected cluster, there is no such catalog source name. > (the existing catalog sources are not being touched if the cluster is > disconnected). > > I addressed these two topics here: > https://gitlab.cee.redhat.com/contra/cnv-qe-automation/-/merge_requests/466 > > Note that I derived that names of the catalog sources according to the old > appregistry namings: > production --> redhat-operators > osbs --> rh-osbs-operators > stage --> redhat-operators-stage > > please confirm if that's correct for the disconnected clusters you are using. > > Thanks Oren, We can agree these are the names of the catalogs in a disconnected cluster.
@ashoshan Will this be verified for 2.5.0 or can I target it to 2.5.1?
Let's postpone to 2.5.1, this is not going to block 2.5.0.
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