Bug 2047463 - Acm failed to install due to some missing CRDs in operator
Summary: Acm failed to install due to some missing CRDs in operator
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Installer
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: rhacm-2.5
Assignee: Jakob
QA Contact: txue
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-27 21:28 UTC by kurwang
Modified: 2022-06-09 02:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-06-09 02:08:48 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.5+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19500 0 None None None 2022-01-27 23:49:20 UTC
Red Hat Product Errata RHSA-2022:4956 0 None None None 2022-06-09 02:09:16 UTC

Description kurwang 2022-01-27 21:28:39 UTC
Description of the problem: When deploying a downstream build of ACM, CRDs were missing in the multiclusterhub operator. Only the placeholder.yaml was there

Operator snapshot version: 2.5.0-DOWNSTREAM-2022-01-26-17-28-39

OCP version: 4.8.27

Browser Info: Firefox

Steps to reproduce:
1. Attempted to a downstream build of ACM using the deploy repo
2. Used snapshot 2.5.0-DOWNSTREAM-2022-01-26-17-28-39

Actual results: MCH was stuck in installing

Expected results: MCH to be in a running state

Additional info: included MCE snapshot in my env variables but wasnt sure if that had any effect.
MCE_SNAPSHOT_CHOICE=2.0.0-DOWNANDBACK-2022-01-24-22-15-45

Console output
❯ oc exec -i -t multiclusterhub-operator-7c45d8c86f-zpvf6 -- bash
bash-4.4$ ls
bin  boot  crds  dev  etc  home  image-manifests  lib  lib64  lost+found  media  mnt  opt  proc  root  run  sbin  srv  sys  tmp  usr  var
bash-4.4$ cd crds/
bash-4.4$ ls
placeholder.yaml
bash-4.4$

Comment 1 Jakob 2022-02-01 17:44:06 UTC
This happened because something that usually happens in a downstream rendering process to make CRDs available went missing in 2.5. It isn't clear how it was lost, maybe during the stolostron rename, but it has been fixed and downstream builds should no longer encounter this issue

Comment 4 errata-xmlrpc 2022-06-09 02:08:48 UTC
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.5 security updates, images, and bug fixes), 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-2022:4956


Note You need to log in before you can comment on or make changes to this bug.