Can't log in to an OpenShift deployment

Hi,

I’m trying to set up a software broker (developer edition) in OpenShift, using the Event Broker Operator. Once the pod’s running, I can get the admin password from the admin-creds secret, but I can’t log into the console, I get a 401 Unauthorized error. I can log into the pod and verify that by looking at the secrets mount. Looking at the pod logs, I see an error:

ERROR: startup-broker.sh-Solace Management API never came up

Could that be the problem?

Thanks,

Michael

Hi there, I’m Solly AI, I generate responses to your questions using the power of the Solace Agent Mesh:

Please remember that AI technology can make mistakes so ensure that you read our Disclaimer.

AI Generated responses are a work in progress, your help in evaluating my response would be awesome! If my response makes sense, please mark it as a solution or give a :+1:. If my response doesn’t make sense for your topic, please react to it with a :shaking_face:.

Since no specific facts were provided about this error scenario in the Solace documentation, I cannot provide a definitive answer about this specific error message. This appears to be a deployment-specific issue that could have multiple potential causes related to authentication, networking, or container configuration in OpenShift.

I recommend:

  1. Checking the Solace documentation for proper OpenShift deployment procedures
  2. Reviewing the container logs for additional error messages
  3. Verifying your OpenShift configuration and permissions

For the most accurate troubleshooting guidance, please search the Solace documentation or review the deployment guides for Solace Event Broker on OpenShift.

Hi @damaru,

Nice to see you around! Are these the steps you are following?

I think the error you are seeing is likely the reason. I imagine you can’t even load the Broker Manager?

Hi Marc,

Thanks for the quick response! Nice to see you’re still around! I ended up logging into the pod, bringing up the CLI and changing the admin password there. Now I can log in. I’m not sure why the credentials didn’t work the usual way, but I’m up and running.

Mike

Great, glad it worked!