openshift / origin-web-console

Web Console for the OpenShift Application Platform
https://www.openshift.org/
Apache License 2.0
123 stars 230 forks source link

OKD Web-console logs you out in a loop after fresh install #3167

Closed welsh1lad closed 3 years ago

welsh1lad commented 4 years ago

OKD 3.11 All in one install, after completion of install script / playbook and configuring user name Im able to login to the console, But then Logged out straight away with error message OOPs Error.

I can replicate this every time: and Have found a resolve:

Inventory file for Authentication is configured as below

openshift_master_identity_providers=[{'name': 'htpasswd_auth', 'login': 'true', 'challenge': 'true', 'kind': 'HTPasswdPasswordIdentityProvider'}]

After deployment is completed I run the following commands on the ALL-IN-ONE node create user htpasswd -c /etc/origin/master/htpasswd admin admin give admin permission oc adm policy add-cluster-role-to-user cluster-admin admin

Then try and login to the webconsole: This then Fails , You get passed the login screen and able to see the webconsole Then presented with 'OOPS Error' Message. You are then presented with login box again.

To Resolve this : Run the same commands again .

htpasswd -c /etc/origin/master/htpasswd admin
admin

give admin permission oc adm policy add-cluster-role-to-user cluster-admin admin

Results: Im now able to login and view and manage the web-console.

This should not be the case , run the above commands once should be enough.

Login box is managed with the following httpd-tools-2.4.6-90.el7.centos.x86_64

openshift is oc version oc v3.11.0+62803d0-1 kubernetes v1.11.0+d4cacc0 features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://master.uat.okd.XXXX.com:8443 openshift v3.11.0+7876dd5-361 kubernetes v1.11.0+d4cacc0

Ansible: Name : ansible Version : 2.6.5 Release : 1.el7.ans Source RPM : ansible-2.6.5-1.el7.ans.src.rpm

openshift-bot commented 3 years ago

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

openshift-bot commented 3 years ago

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity. Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten /remove-lifecycle stale

openshift-bot commented 3 years ago

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen. Mark the issue as fresh by commenting /remove-lifecycle rotten. Exclude this issue from closing again by commenting /lifecycle frozen.

/close

openshift-ci-robot commented 3 years ago

@openshift-bot: Closing this issue.

In response to [this](https://github.com/openshift/origin-web-console/issues/3167#issuecomment-734991754): >Rotten issues close after 30d of inactivity. > >Reopen the issue by commenting `/reopen`. >Mark the issue as fresh by commenting `/remove-lifecycle rotten`. >Exclude this issue from closing again by commenting `/lifecycle frozen`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.