Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-20768

Changing simpleCryptoBackendSecret does not trigger a reconcile

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • rhos-18.0.9
    • barbican-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Moderate

      To Reproduce Steps to reproduce the behavior:

      1. Deploy a barbican instance using barbican-operator
      2. Create a secret to hold only the KEK that is not the default osp-secret
      3. Edit the barbican CR (or openstackcontrolplane CR) to change the value of 
        spec:
          simpleCryptoBackendSecret: not-osp-secret
      4. This causes a reconcile of the barbican deployment wich results in new barbican Pods (expected)
      5. Now, edit not-osp-secret
      6. Changing this Secret should trigger a reconcile again to pick up the changes, but it appears that the operator is not watching the Secret because no reconcile is triggered and now new Pod is created.

      Expected behavior

      • Editing the secret triggers another reconciliation of the barbican CR

      Screenshots

      • Attached Image

      Device Info (please complete the following information):

      • Hardware Specs: [e.g. Apple M2 Pro Chip, 16 GB Memory, etc.]
      • OS Version: [e.g. Mac OS 14.4.1, Fedora Linux 40]
      • InstructLab Version: [output of \\\\{{{}ilab --version{}}}]
      • Provide the output of these two commands:
        • sudo bootc status --format json | jq .status.booted.image.image.image to print the name and tag of the bootc image, should look like registry.stage.redhat.io/rhelai1/bootc-intel-rhel9:1.3-1732894187
        • ilab system info to print detailed information about InstructLab version, OS, and hardware – including GPU / AI accelerator hardware

      Bug impact

      • Please provide information on the impact of this bug to the end user.

      Known workaround

      • Please add any known workarounds.

      Additional context

      • <your text here>

              Unassigned Unassigned
              dmendiza Douglas Mendizabal
              rhos-dfg-security
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: