-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
openshift-apiserver drops out temporarily after install. #813
Comments
On AWS, there are three openshift-apiservers; one is about a minute or two older than the others. The newer ones started right around the time this problem occurred. |
Log from "older" openshift-apiserver:
|
Log from one of the "newer" openshift-apiservers:
|
Cross-linking openshift/origin#21612. |
On libvirt an api server drop is expected. On aws, I wouldn't. Based on the message and the user, this worth checking with @enj for the new authenticator. |
This is very definitely happening on AWS also. |
I think this might have been resolved by openshift/machine-config-operator#225. Can anyone still reproduce? If not, can we close this? |
I didn't observe it on either aws or libvirt; go ahead and close it. |
/close |
@wking: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Version
Platform (aws|libvirt|openstack):
AWS and libvirt
What happened?
After the installer completed (immediately on AWS, about 7 minutes later on libvirt), I was able to
oc login
. A few minutes later, I was no longer able to; I got 400 messages on the command line. Shortly thereafter (within a few minutes), I was then able to interact, and it stayed up.On AWS, I was able to narrow the time down to within maybe 20 seconds prior to 20:09:01 UTC.
What you expected to happen?
Once I'm able to log in, I expect to be able to interact with either the CLI or the console without interruption.
How to reproduce it (as minimally and precisely as possible)?
After the installer completes, run
oc login -u kubeadmin -p <password>
until the login succeeds.Run
oc get routes --all-namespaces
(or any similar command) repeatedly.After several minutes, observe
If you try to run
oc login
, observeThe text was updated successfully, but these errors were encountered: