Giters

stolostron / deploy

Deploy Development Builds of Open Cluster Management (OCM) on RedHat Openshift Container Platform

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[BUG][DEPLOY] Unable to install acm-custom-registy using start.sh

vthapar opened this issue · comments

commented

Describe the bug
Tried installing ACM using ./start.sh --watch with snapshot 2.6.0-SNAPSHOT-2022-07-13-23-23-00 but it fails to install acm-custom-registry.

To Reproduce
Steps to reproduce the behavior:

  1. Export KUBECONFIG to the kubeconfig for the OCP cluster
  2. Run ./start.sh --watch
  3. Use 2.6.0-SNAPSHOT-2022-07-13-23-23-00 snapshot
  4. Installation fails because acm-custom-registry pods don't come up

Expected behavior
acm-custom-registry pods to come up and installation to complete

Screenshots

./start.sh --watch --silent
* Testing connection
* Using baseDomain: vthapar-acmhub.subm.red-chesterfield.com
* oc CLI Client Version: 4.11.0-rc.2
* Silent mode
* Applying multicluster-hub-cr values
Error: open /tmp/temp2200282646: no such file or directory
Error: open /tmp/temp1294710551: no such file or directory
catalogsource.operators.coreos.com/acm-custom-registry created

#####
Wait for acm-custom-registry to reach running state (4min).
* STATUS: Waiting
--snip--
* STATUS: Waiting
Timeout waiting for the acm-custom-registry. Try cleaning up using the uninstall scripts before running again.
List of current pods:
NAME                                    READY   STATUS    RESTARTS   AGE
certified-operators-w74dj               1/1     Running   0          39m
community-operators-8nt2m               1/1     Running   0          39m
marketplace-operator-5789466757-wsvmd   1/1     Running   0          42m
redhat-marketplace-hf2kb                1/1     Running   0          39m
redhat-operators-b6bfz                  1/1     Running   0          39m

Desktop (please complete the following information):

  • OS: Fedora34
  • Browser N.A.
  • Snapshot 2.6.0-SNAPSHOT-2022-07-13-23-23-00

Additional context
OCP Version:

oc version
Client Version: 4.11.0-rc.2
Kustomize Version: v4.5.4
Server Version: 4.11.0-rc.1
Kubernetes Version: v1.24.0+2dd8bb1

acm-custom-registry CatalogSource has following error in its status:

status:
  message: 'image and address unset: at least one must be set for sourcetype: grpc'
  reason: SpecInvalidError
commented

Update:

Failure was caused by yq eval -i yq was installed through snapd. It was same issue as mikefarah/yq#786 and directly downloading the binary seems to have resolved the issue. Still not sure why it used to work earlier but stopped working recently. Probably yq was updated by snapd auto-refresh?

Maybe add a note/warning in README for yq to not use snapd on Fedora?