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

With tls-e configured, if a controller is rebooted, no apis/horizon/etc work properly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • keystone-operator
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • ?
    • None
    • Moderate

      With tls-e configured, if a controller is rebooted, no apis/horizon/etc work properly.    The issue appears to come from the dogpile.cache.pymemcache module that is used when  MemachedTLS is enabled. If TLS is not used, it defaults to the dogpile.cache.memcached module and that seems to operate as expected.

      2025-09-24 12:00:49.082 32 ERROR keystone.server.flask.request_processing.middleware.auth_context     super().connect(addr)
2025-09-24 12:00:49.082 32 ERROR keystone.server.flask.request_processing.middleware.auth_context ConnectionRefusedError: [Errno 111] Connection refused
2025-09-24 12:00:49.082 32 ERROR keystone.server.flask.request_processing.middleware.auth_context

              Unassigned Unassigned
              rhn-support-dhill Dave Hill
              rhos-dfg-security
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: