Bug 2106069 - Upgrade to 2.5.1 from 2.5.0 fails due to missing Subscription CRD
Summary: Upgrade to 2.5.1 from 2.5.0 fails due to missing Subscription CRD
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.5
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: rhacm-2.5.2
Assignee: Mike Ng
QA Contact: Almen Ng
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-11 17:02 UTC by James Young
Modified: 2025-10-03 12:34 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-13 20:06:28 UTC
Target Upstream Version:
Embargoed:
dho: qe_test_coverage-
bot-tracker-sync: rhacm-2.5.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 24158 0 None None None 2022-07-11 19:36:19 UTC
Red Hat Product Errata RHSA-2022:6507 0 None None None 2022-09-13 20:06:41 UTC

Comment 3 juhsu 2022-07-12 17:44:26 UTC
Updates from the acm-prio distro:

Mike Ng:
I think we will need the install team and most likely the Openshift OLM team to take a look.
We did not update the App Subscription CRD in the app lifecycle related 2.5.1 fix.

The App Subscription CRD is bundled in the CSV which is handled by the OCP OLM, and it seems like during the upgrade of 2.5 to 2.5.1, it got removed.

Jakob Gray:
I agree we need to reapply the CRD. I don't think there is anything needed for the installer before doing this.

James Young:
Thanks team, could we please confirm the steps for re-applying the CRD? If we can get the going that would be great and I could pivot towards OLM for an RCA. We do have an OCP must-gather that includes the OLM logs at https://attachments.access.redhat.com/hydra/rest/cases/03263791/attachments/8aeb2aac-0ccf-463e-abb8-f387e58e67a5?usePresignedUrl=true

A lot of:
2022-07-10T11:27:25.687600978+00:00 stderr F E0710 11:27:25.687570       1 queueinformer_operator.go:290] sync {"update" "open-cluster-management/advanced-cluster-management.v2.5.1"} failed: requirements were not met

Jakob Gray:
I believe the best method is to delete and reinstall the ACM operator. The MCH will persist so only a few operator deployments would be recreated in the process. 

James Young:
And that will have no impact on managed clusters / applications / policies / etc right?

Jakob Gray:
Correct.

Comment 4 juhsu 2022-07-12 17:46:11 UTC
@jayoung Can you provide an update here with the results of the OCP OLM investigation?  Want to make sure there isn't a problem with the ACM upgrade somewhere.

Comment 8 Ezequiel Hector Brizuela 2022-08-01 13:36:20 UTC
Any update regarding this? I need to make an update to the customer about this.

~ ebrizuel ~

Comment 11 Ishmam Amin 2022-09-02 15:11:29 UTC
All missing CRD's are present in 2.5.2 version

Comment 12 Derek Ho 2022-09-02 15:38:04 UTC
was testing on fresh installation. Need to verify the CRDs in an upgraded env.

Comment 13 Ishmam Amin 2022-09-02 18:52:05 UTC
CRD's are present in upgraded env (2.5.2) upgraded from 2.5.1

Comment 18 errata-xmlrpc 2022-09-13 20:06:28 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 (Critical: Red Hat Advanced Cluster Management 2.5.2 security fixes 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:6507

Comment 19 Red Hat Bugzilla 2023-09-18 04:41:43 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days


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