Bug 2064722
Summary: | [Tracker] [DR][ACM 2.5] Applications are not getting deployed on managed cluster | ||
---|---|---|---|
Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Sidhant Agrawal <sagrawal> |
Component: | App Lifecycle | Assignee: | Mike Ng <ming> |
Status: | CLOSED ERRATA | QA Contact: | Napoco Agbetra <nagbetra> |
Severity: | urgent | Docs Contact: | bswope <bswope> |
Priority: | unspecified | ||
Version: | rhacm-2.5 | CC: | bmekhiss, dhuynh, gallwasingeborg, huichen, juhsu, kramdoss, kseeger, madam, mmuench, muagarwa, nagbetra, ocs-bugs, prsurve, xiangli, ykaul, yuhe |
Target Milestone: | --- | Keywords: | TestBlocker |
Target Release: | rhacm-2.5 | Flags: | bot-tracker-sync:
rhacm-2.5+
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-06-09 02:09:46 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 2058220 |
Description
Sidhant Agrawal
2022-03-16 12:23:53 UTC
There is a backward compatibility issue with ACM 2.5. For DR, The PlacementRule for a subscription is created with Ramen as the scheduler. Like this: ``` spec: clusterConditions: - status: "True" type: ManagedClusterConditionAvailable clusterReplicas: 1 schedulerName: ramen ``` When Ramen is the scheduler, the PlacementRule will not decide on the location of the subscription, but rather, it depends on Ramen to tell it in which location the subscription is supposed to be placed. ``` status: decisions: - clusterName: sagrawal-c1 clusterNamespace: sagrawal-c1 ``` In this case, the *.status.decisions* is updated by Ramen. Since we upgraded to ACM 2.5 this has stopped working as expected. In other words, If the .spec.schedulerName is set to *ramen*, even though Ramen updates the status decisions, the subscription for the target managedcluster will NOT be created. The workaround is to set the clusterSelector and remove the schedulerName from the spec section similar to this ``` spec: clusterSelector: matchLabels: name: sagrawal-c1 status: decisions: - clusterName: sagrawal-c1 clusterNamespace: sagrawal-c1 ``` This is definitely a blocker. The workaround will require Ramen to change. This is not an option for the DR team at this point. We will request a fix from the appLC team. An issue against ACM has been opened here: https://github.com/stolostron/backlog/issues/20789 (In reply to Benamar Mekhissi from comment #5) > An issue against ACM has been opened here: > https://github.com/stolostron/backlog/issues/20789 Invalid link? The link is valid. You just have to have rights access to the stolostron backlog. (In reply to Benamar Mekhissi from comment #7) > The link is valid. You just have to have rights access to the stolostron > backlog. Thanks - who do I have to ask to get access? (surprised somewhat to see a private repo on github). (In reply to Yaniv Kaul from comment #8) > (In reply to Benamar Mekhissi from comment #7) > > The link is valid. You just have to have rights access to the stolostron > > backlog. > > Thanks - who do I have to ask to get access? (surprised somewhat to see a > private repo on github). You need to send request to forum-amc-devops similar to this: https://coreos.slack.com/archives/CSZLMKPS5/p1647533098820809 G2Bsync 1077903053 comment mikeshng Thu, 24 Mar 2022 18:10:12 UTC G2Bsync `2.5.0-SNAPSHOT-2022-03-24-17-14-58` build should contain the fix. Please ignore the last bot-tracker-sync comment Verified the bug fix on ACM side (ACM 2.5) The hub subscription controller reconciles the subscription to read the cluster decision and propagate to the cluster 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 I trust you will post more like that later on. https://www.dg-paystub.com/ |