Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-376

[2275320] [RDR] [Hub recovery] [Co-situated] lastGroupSyncTime info is lost post hub recovery for all the workloads which are primary on down managed cluster

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • None
    • odf-4.15
    • odf-dr/ramen
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • 4.16.0-124
    • ?
    • Hide
      .Information about `lastGroupSyncTime` is lost after hub recovery for the workloads that are primary on the unavailable managed cluster

      Applications that are previously failedover to a managed cluster do not report a `lastGroupSyncTime`, thereby causing the trigger of the alert `VolumeSynchronizationDelay`. This is because when the ACM hub and a managed cluster, that are part of the DRPolicy are unavailable, a new ACM hub cluster is reconstructed from the backup.

      Workaround: If the managed cluster to which the workload was failed over is unavailable, you can still failover to a surviving managed cluster.
      Show
      .Information about `lastGroupSyncTime` is lost after hub recovery for the workloads that are primary on the unavailable managed cluster Applications that are previously failedover to a managed cluster do not report a `lastGroupSyncTime`, thereby causing the trigger of the alert `VolumeSynchronizationDelay`. This is because when the ACM hub and a managed cluster, that are part of the DRPolicy are unavailable, a new ACM hub cluster is reconstructed from the backup. Workaround: If the managed cluster to which the workload was failed over is unavailable, you can still failover to a surviving managed cluster.
    • Known Issue
    • RamenDR sprint 2024 #11
    • None

      Description of problem (please be detailed as possible and provide log
      snippests):

      Version of all relevant components (if applicable):
      ACM 2.10.1 GA'ed
      MCE 2.5.2
      ODF 4.15.1-1
      ceph version 17.2.6-196.el9cp (cbbf2cfb549196ca18c0c9caff9124d83ed681a4) quincy (stable)
      OCP 4.15.0-0.nightly-2024-04-07-120427
      Submariner 0.17.0 GA'ed
      VolSync 0.9.1

      Platform- VMware

      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?

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

      Can this issue reproducible?

      Can this issue reproduce from the UI?

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

      Steps to Reproduce:
      ****Active hub co-situated with primary managed cluster****

      1. After site failure (where active hub and the primary managed cluster goes down together), perform hub recovery and move to passive hub.
      2. Ensure the available managed cluster is successfully imported on the RHACM console, and DRPolicy gets validated.
      3. When drpc is restored, check the lastGroupSyncTime for all the workloads which are primary on the down managed cluster.

      It will be reset to null.

      Actual results: [RDR] [Hub recovery] [Co-situated] lastGroupSyncTime info is lost post hub recovery for all the workloads which are primary on down managed cluster

      The info. is fetched from the VRG of each workload per namespace and is lost when the cluster becomes unavailable.

      Expected results: Fetch the lastGroupSyncTime from S3 store of available managed cluster which is still up and running instead of VRG of the primary managed cluster which goes down during site failure and currently this info is lost due to cluster's unavailability.

      Additional info:

              bmekhiss Benamar Mekhissi
              amagrawa@redhat.com Aman Agrawal
              Aman Agrawal, Anjana Sriram, Benamar Mekhissi
              Aman Agrawal Aman Agrawal
              Votes:
              0 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated: