After upgrading RH-SSO for OpenShift to tag "7.5-33" or 7.6, the pod fails to start with CrashLoopBackOff

Solution Unverified - Updated -

Issue

  • After upgrading RH-SSO for OpenShift to tag "7.5-33" or 7.6, the pod fails to start with CrashLoopBackOff when ENABLE_ACCESS_LOG=true
  • The pod log show following error:
[0m[31m09:32:35,772 ERROR [org.jboss.as.controller] (Controller Boot Thread) 

OPVDX001: Validation error in standalone-openshift.xml -------------------------
|
|  649:     <host name="default-host" alias="localhost">
|  650:         <location name="/" handler="sso-welcome-content"/>
|  651:         <access-log use-server-log="true" pattern="%h %l %u %t %{i,X-Forwarded-Host} \<!-- ##ACCESS_LOG_VALVE## -->quot;%r\<!-- ##ACCESS_LOG_VALVE## -->quot; %s %b"/>
|                                                                                             ^^^^ Unexpected character '<' (code 60) in attribute value
|
|  652:         <http-invoker security-realm="ApplicationRealm"/>
|  653:     </host>
|  654: </server>

Environment

  • Red Hat Single Sign-On (RH-SSO) for OpenShift
    • tag "7.5-33" or later
    • tag "7.6-10" or before

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content