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

If HeatAuthEncryptionKey is not at least 32 characters long, Heat pods CrashLoop

XMLWordPrintable

    • Heat Service pods CrashLoopBackOff with short HeatAuthEncryptionkey
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • No Docs Impact
    • ?
    • ?
    • 0% To Do, 0% In Progress, 100% Done
    • Automated

      Description:
      When you enable Heat, you need to have done so with a HeatAuthEncryptionKey in the `osp-secret` that is at least 32 Characters long. If the key provided is less than that, the Heat service pods will CrashLoopBackOff until it's corrected.

      Expectation:
      Instead of allowing the pods to be created and then expecting operators to check the service pod logs, we should instead validate the secret length in the Heat operator before reconciling the service pods. This will allow us to report the issue via the Heat CR status.conditions which is more user friendly and intuitive for users.

              rhn-support-bshephar Brendan Shephard
              rhn-support-bshephar Brendan Shephard
              rhos-dfg-df
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: