Bug 2232552 - [RDR] DRPC Deployment is failing after assigning DRPolicy to the application
Summary: [RDR] DRPC Deployment is failing after assigning DRPolicy to the application
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenShift Data Foundation
Classification: Red Hat Storage
Component: odf-dr
Version: 4.14
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ODF 4.14.0
Assignee: Shyamsundar
QA Contact: Sidhant Agrawal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-17 10:50 UTC by Sidhant Agrawal
Modified: 2023-11-08 18:55 UTC (History)
7 users (show)

Fixed In Version: 4.14.0-117
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 18:54:15 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2023:6832 0 None None None 2023-11-08 18:55:04 UTC

Description Sidhant Agrawal 2023-08-17 10:50:49 UTC
Description of problem (please be detailed as possible and provide log
snippests):
After assigning DRPolicy to Application set or Subscription type applications, DRPC does not reach "Deployed" state

DRPC resource shows below error:
...
message: 'placementdecisions.cluster.open-cluster-management.io "busybox-appset-placement-decision-1"
        is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to
        a resource you can''t set finalizers on: , <nil>'
...


Version of all relevant components (if applicable):
OCP: 4.14.0-ec.4
ODF: 4.14.0-110
ceph version 17.2.6-107.el9cp (4079b48a400e4d23864de0da6d093e200038d7fb) quincy (stable)
ACM: 2.9.0-92 (image: quay.io:443/acm-d/acm-custom-registry:2.9.0-DOWNSTREAM-2023-08-15-16-50-58)
Submariner 0.16.0 (Globalnet enabled) (image: brew.registry.redhat.io/rh-osbs/iib:552428)
VolSync: 0.7.3

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?

Is there any workaround available to the best of your knowledge?
NA

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
2

Can this issue reproducible?
Yes

Can this issue reproduce from the UI?
Yes

If this is a regression, please provide more details to justify this:
Yes

Steps to Reproduce:
1. Configure RDR setup
2. Deploy Application set type sample application
3. Go to Applications page -> Manage data policy -> Assign policy
4. Observe the DRPC status
5. Deploy Subscription type sample application
6. Go to Applications page -> Manage data policy -> Assign policy
7. Observe DRPC status

Actual results:
DRPC currentstate does not reach "Deployed" 

Expected results:
DRPC currentstate should reach "Deployed" 

Additional Info:

DRPC output:
------
NAMESPACE          NAME                            AGE   PREFERREDCLUSTER   FAILOVERCLUSTER   DESIREDSTATE   CURRENTSTATE   PROGRESSION   START TIME   DURATION   PEER READY
busybox-sub        busybox-sub-placement-1-drpc    19m   sagrawal-c1                                                                                              True
openshift-gitops   busybox-appset-placement-drpc   30m   sagrawal-c1                                                                                              True

$ oc get drpc -A -o yaml
apiVersion: v1
items:
- apiVersion: ramendr.openshift.io/v1alpha1
  kind: DRPlacementControl
  metadata:
    annotations:
      drplacementcontrol.ramendr.openshift.io/last-app-deployment-cluster: sagrawal-c1
    creationTimestamp: "2023-08-17T10:14:45Z"
    finalizers:
    - drpc.ramendr.openshift.io/finalizer
    generation: 1
    labels:
      cluster.open-cluster-management.io/backup: resource
    name: busybox-sub-placement-1-drpc
    namespace: busybox-sub
    resourceVersion: "881610"
    uid: c00ae7e6-7f43-4c76-b9ff-e215198c424b
  spec:
    drPolicyRef:
      apiVersion: ramendr.openshift.io/v1alpha1
      kind: DRPolicy
      name: odr-policy-5m
    placementRef:
      apiVersion: cluster.open-cluster-management.io/v1beta1
      kind: Placement
      name: busybox-sub-placement-1
      namespace: busybox-sub
    preferredCluster: sagrawal-c1
    pvcSelector:
      matchLabels:
        appname: busybox
  status:
    conditions:
    - lastTransitionTime: "2023-08-17T10:14:45Z"
      message: 'placementdecisions.cluster.open-cluster-management.io "busybox-sub-placement-1-decision-1"
        is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to
        a resource you can''t set finalizers on: , <nil>'
      observedGeneration: 1
      reason: none
      status: Unknown
      type: Available
    - lastTransitionTime: "2023-08-17T10:14:45Z"
      message: Initialization
      observedGeneration: 1
      reason: Initiating
      status: "True"
      type: PeerReady
    lastUpdateTime: "2023-08-17T10:14:45Z"
    preferredDecision: {}
    resourceConditions:
      resourceMeta:
        generation: 0
        kind: ""
        name: ""
        namespace: ""
- apiVersion: ramendr.openshift.io/v1alpha1
  kind: DRPlacementControl
  metadata:
    annotations:
      drplacementcontrol.ramendr.openshift.io/last-app-deployment-cluster: sagrawal-c1
    creationTimestamp: "2023-08-17T10:03:38Z"
    finalizers:
    - drpc.ramendr.openshift.io/finalizer
    generation: 1
    labels:
      cluster.open-cluster-management.io/backup: resource
    name: busybox-appset-placement-drpc
    namespace: openshift-gitops
    resourceVersion: "871871"
    uid: 8f895571-2639-486c-9910-62ba1c231b41
  spec:
    drPolicyRef:
      apiVersion: ramendr.openshift.io/v1alpha1
      kind: DRPolicy
      name: odr-policy-5m
    placementRef:
      apiVersion: cluster.open-cluster-management.io/v1beta1
      kind: Placement
      name: busybox-appset-placement
      namespace: openshift-gitops
    preferredCluster: sagrawal-c1
    pvcSelector:
      matchLabels:
        appname: busybox
  status:
    conditions:
    - lastTransitionTime: "2023-08-17T10:03:38Z"
      message: 'placementdecisions.cluster.open-cluster-management.io "busybox-appset-placement-decision-1"
        is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to
        a resource you can''t set finalizers on: , <nil>'
      observedGeneration: 1
      reason: none
      status: Unknown
      type: Available
    - lastTransitionTime: "2023-08-17T10:03:38Z"
      message: Initialization
      observedGeneration: 1
      reason: Initiating
      status: "True"
      type: PeerReady
    lastUpdateTime: "2023-08-17T10:03:38Z"
    preferredDecision: {}
    resourceConditions:
      resourceMeta:
        generation: 0
        kind: ""
        name: ""
        namespace: ""
kind: List
metadata:
  resourceVersion: ""


Resources on managed cluster (sagrawal-c1)
-------
> App-1 resources:
$ oc get pods,pvc,vr,vrg -o wide -n busybox-appset
NAME                          READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
pod/busybox-d549f9d85-gphjs   1/1     Running   0          33m   10.133.2.84   compute-1   <none>           <none>

NAME                                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                  AGE   VOLUMEMODE
persistentvolumeclaim/busybox-pvc   Bound    pvc-ee5630fc-30d0-4c65-b81a-44634d25f978   5Gi        RWO            ocs-storagecluster-ceph-rbd   33m   Filesystem

NAME                                                             AGE   VOLUMEREPLICATIONCLASS                  PVCNAME       DESIREDSTATE   CURRENTSTATE
volumereplication.replication.storage.openshift.io/busybox-pvc   31m   rbd-volumereplicationclass-1625360775   busybox-pvc   primary        Primary

NAME                                                                        DESIREDSTATE   CURRENTSTATE
volumereplicationgroup.ramendr.openshift.io/busybox-appset-placement-drpc   primary        Primary

> App-2 resources
$ oc get pods,pvc,vr,vrg -o wide -n busybox-sub
NAME                          READY   STATUS    RESTARTS   AGE   IP            NODE        NOMINATED NODE   READINESS GATES
pod/busybox-d549f9d85-wls59   1/1     Running   0          21m   10.133.2.85   compute-1   <none>           <none>

NAME                                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                  AGE   VOLUMEMODE
persistentvolumeclaim/busybox-pvc   Bound    pvc-0f36fafc-4cc7-4492-9fd6-bd5d70a2d091   5Gi        RWO            ocs-storagecluster-ceph-rbd   21m   Filesystem

NAME                                                             AGE   VOLUMEREPLICATIONCLASS                  PVCNAME       DESIREDSTATE   CURRENTSTATE
volumereplication.replication.storage.openshift.io/busybox-pvc   21m   rbd-volumereplicationclass-1625360775   busybox-pvc   primary        Primary

NAME                                                                       DESIREDSTATE   CURRENTSTATE
volumereplicationgroup.ramendr.openshift.io/busybox-sub-placement-1-drpc   primary        Primary


Mirroring status on both managed clusters:
-------
$ oc get cephblockpool ocs-storagecluster-cephblockpool -n openshift-storage -o jsonpath='{.status.mirroringStatus.summary}{"\n"}'
{"daemon_health":"OK","health":"OK","image_health":"OK","states":{"replaying":2}}

Comment 6 avdhoot 2023-08-22 11:14:17 UTC
Observed Same issue in MDR also 


avd@Avdhoots-MacBook-Pro hub % oc get drpc -A -o yaml | grep status -A 5
  status:
    conditions:
    - lastTransitionTime: "2023-08-22T07:59:43Z"
      message: 'placementdecisions.cluster.open-cluster-management.io "busybox-cephfs-placement-1-decision-1"
        is forbidden: cannot set blockOwnerDeletion if an ownerReference refers to
        a resource you can''t set finalizers on: , <nil>'

avd@Avdhoots-MacBook-Pro hub % oc get drpc -A -o wide                   
NAMESPACE        NAME                              AGE     PREFERREDCLUSTER   FAILOVERCLUSTER   DESIREDSTATE   CURRENTSTATE   PROGRESSION   START TIME   DURATION   PEER READY
busybox-cephfs   busybox-cephfs-placement-1-drpc   3h12m   asagare-c1                                                                                               True

Comment 8 Mudit Agarwal 2023-08-24 02:23:15 UTC
Do we have an ACM build with this change?

Comment 19 errata-xmlrpc 2023-11-08 18:54:15 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 OpenShift Data Foundation 4.14.0 security, enhancement & bug fix update), 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-2023:6832


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