Bug 2059954 - Subscriptions stop reconciling after channel secrets are recreated
Summary: Subscriptions stop reconciling after channel secrets are recreated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: App Lifecycle
Version: rhacm-2.4.z
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: rhacm-2.4.3
Assignee: Roke Jung
QA Contact: Rafat Islam
bswope@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-02 11:58 UTC by Mihir Lele
Modified: 2022-04-20 23:48 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-20 23:47:37 UTC
Target Upstream Version:
Embargoed:
bot-tracker-sync: rhacm-2.4.z+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 20358 0 None None None 2022-03-02 15:12:56 UTC
Red Hat Product Errata RHSA-2022:1476 0 None None None 2022-04-20 23:48:31 UTC

Description Mihir Lele 2022-03-02 11:58:46 UTC
Description of the problem:

After the deletion of all channel secrets, RHACM started failing reconciling subscriptions due to missing secret, which is expected. But when secret for main subscription was restored, The reconciling was not automatically invoked.

Release version: ACM 2.4.1

OCP version: 4.9

Steps to reproduce:

1) Create 10+ channels with the reconcile rate set to "high" that access private git repositories

2) Create 30+ subscriptions that utilise 10+ channels

3) Check that subscriptions successfully reconciled

4) Delete all secrets from all namespaces that are used by channels

5) Observe multicluster-hub logs for errors

6) Introduce change to subscription

7) Restore only one secret for one of the channels

Subscription never reconciles

Additional info:

Comment 12 errata-xmlrpc 2022-04-20 23:47:37 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 (Moderate: Red Hat Advanced Cluster Management 2.4.3 security updates 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:1476


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