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

[2176045] Mirroring between clusters with MCG is not working

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • odf-4.12.z
    • odf-4.12
    • Documentation
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 4.12.z
    • ?
    • ?
    • If docs needed, set a value
    • None

      Description of problem (please be detailed as possible and provide log
      snippests):
      Mirroring between clusters with MCG is not working.

      Version of all relevant components (if applicable): odf-operator.v4.12.0

      Does this issue impact your ability to continue to work with the product
      (please explain in detail what is the user impact)?
      Yes, the mirroring is needed for a partner use case.

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

      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

      Steps to Reproduce:
      1. Configure a BackingStore with an S3 storage endpoint from another cluster:
      apiVersion: noobaa.io/v1alpha1
      kind: BackingStore
      metadata:
      finalizers:

      • noobaa.io/finalizer
        labels:
        app: noobaa
        name: bs-staging01
        namespace: openshift-storage
        spec:
        s3Compatible:
        endpoint: http://s3-openshift-storage.apps.staging01.esmb.bos2.lab
        secret:
        name: backingstore-staging-secret
        namespace: openshift-storage
        signatureVersion: v4
        targetBucket: oadp-bucket-1a0b629c-b9d4-451c-b073-012f6e701f5d
        type: s3-compatible

      $ oc get backingstore -A
      NAMESPACE NAME TYPE PHASE AGE
      openshift-storage bs-staging s3-compatible Ready 3h26m
      openshift-storage noobaa-default-backing-store s3-compatible Ready 3d17h

      2. Configure a BucketClass with a mirroring policy:
      apiVersion: noobaa.io/v1alpha1
      kind: BucketClass
      metadata:
      labels:
      app: noobaa
      name: bucket-class-test
      namespace: openshift-storage
      spec:
      placementPolicy:
      tiers:

      • backingStores:
      • noobaa-default-backing-store
      • bs-staging
        placement: Mirror

      $ oc get bucketclass -A
      NAMESPACE NAME PLACEMENT NAMESPACEPOLICY QUOTA PHASE AGE
      openshift-storage bucket-class-test {"tiers":[

      {"backingStores":["noobaa-default-backing-store","bs-staging"],"placement":"Mirror"}

      ]} Ready 169m
      openshift-storage noobaa-default-bucket-class {"tiers":[

      {"backingStores":["noobaa-default-backing-store"]}

      ]}

      3. Add the following lines to the ObjectBucketClaim:
      spec:
      additionalConfig:
      bucketclass: bucket-class-test

      Actual results:
      The mirroring is not done and Noobaa log showing:
      Feb-27 11:22:08.536 [BGWorkers/37] [L0] core.server.bg_services.mirror_writer:: no buckets with mirror policy. nothing to do

      Expected results:
      The mirroring should be done.

      Additional info:
      Followed this doc to do the configuration: https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.12/html/managing_hybrid_and_multicloud_resources/mirroring-data-for-hybrid-and-multicloud-buckets

              kbg@redhat.com Kusuma BG
              saledort@redhat.com Sabina Aledort
              Neha Berry Neha Berry
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: