Uploaded image for project: 'OpenShift API for Data Protection'
  1. OpenShift API for Data Protection
  2. OADP-5647

Independent BSL conflicts with DPA BSL when default: true is set.

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • OADP 1.4.4
    • OADP 1.4.3
    • Documentation
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ToDo
    • Sprint 5-MMSDOCS 2025
    • 1
    • 0
    • Very Likely
    • 0
    • None
    • Unset
    • Unknown
    • None

      Description of problem:

      When we create an independent BSL with default: true, and there is already a BSL created through DPA, The new BSL created replaces the DPA BSL to become default.

      Version-Release number of selected component (if applicable):

      1.4, 1.5

      How reproducible:

      Always

      Steps to Reproduce:
      1. Create a DPA with BSL default: true
      2. Create another independent BSL outside of DPA , and keep default: true

      Actual results:

      It gets created and replaces the DPA BSL to become default, and the DPA BSL starts getting validated every second.

      Expected results:

      A documentation to clearly avoid this scenario.

      Additional info:

      $ oc get bsl
      NAME PHASE LAST VALIDATED AGE DEFAULT
      mybsl Available 25s 3m11s true (INDEPENDENT BSL)
      ts-dpa-1 Available 0s 130m (DPA BSL)

              rhn-support-shdeshpa Shruti Deshpande
              rhn-support-ssingla Sachin Singla
              Sachin Singla Sachin Singla
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: