Bug 1656237

Summary: Cluster Admin Console gives error "Application is not available: The application is currently not serving requests at this endpoint. It may not have been started or is still starting."
Product: OpenShift Container Platform Reporter: Candace Sheremeta <cshereme>
Component: Management ConsoleAssignee: Samuel Padgett <spadgett>
Status: CLOSED NOTABUG QA Contact: Yadan Pei <yapei>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, cshereme, dmoessne, jokerman, mmccomas, yapei
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-12 16:09:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of error none

Description Candace Sheremeta 2018-12-05 01:07:18 UTC
Created attachment 1511511 [details]
screenshot of error

Description of problem:

On OCP 3.11 deployments, the Cluster Admin Console (which should be installed by default) does not seem to work, and gives the error seen in the screenshot. I have tried this on two different 3.11 deployments, and I have a customer hitting this issue as well.

oc logs for openshift-console pod in sharedocp311.lab.rdu.cee.redhat.com only show:

2018/12/5 00:32:03 server: authentication failed: http: named cookie not present

attaching screenshot of error and output from `oc describe all` in openshift-console namespace from quicklab 3.11 deployment

I am also asking the cu to provide the output of `oc describe all` from their openshift-console project. please let me know what else we can provide.

Comment 2 Samuel Padgett 2018-12-05 02:41:32 UTC
Can you check that the `consoleBaseAddress` in config map `console-config` in the `openshift-console` namespace matches what you expect? It should be the same as the hostname of route `console`. (I don't think it matches from the screenshot.)

If `consoleBaseAddress` is wrong, update the config map with the correct value and delete the current console pod to force a reload of the config.