OpenShift Kibana Started to Redirect to master1 instead of Public Master URL after Ansible Update

From NovaOrdis Knowledge Base
Jump to navigation Jump to search

Internal

Overview

In an attempt to troubleshoot a Kibana login loop, kibana-proxy OAuth client was deleted, and the openshif-logging.yml Ansible playbook was re-run to reconfigure logging, as described here: https://docs.openshift.com/container-platform/latest/install_config/aggregate_logging.html#troubleshooting-kibana. After that, the authentication redirects issued by Kibana would go to https://master1/... instead of https://master.openshift.novaordis.io/...

Solution

The behavior was caused by the fact that the "OAP_PUBLIC_MASTER_URL" environment variable injected into the "logging-kibana" pod was set to https://master1:443 (cause unknown). The fix was to modify the "logging-kibana" DeploymentConfig: 

oc edit dc/logging-kibana

and set: 

spec:
 ...
 template:
   ...
   - env:
       ...
       - name: OAP_PUBLIC_MASTER_URL
         value: https://master.openshift.novaordis.io
       - name: OAP_LOGOUT_REDIRECT
         value: https://master.openshift.novaordis.io/console/logout
Retrieved from "https://kb.novaordis.com/index.php?title=OpenShift_Kibana_Started_to_Redirect_to_master1_instead_of_Public_Master_URL_after_Ansible_Update&oldid=29279"