-
Notifications
You must be signed in to change notification settings - Fork 232
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
All Masters Never Become Ready #35
Comments
Odd - it got a network configuration, but just... hung. It uses the stock operator-sdk. @shawn-hurley, any thoughts how this could happen? What does |
No openshift-sdn namespace in this cluster. Is that bad? |
The next time this happens, watch the cluster-network-operator to see if its making progress. If not, we need to find out why. |
Still happening this morning:
|
May be an issue on our side, we're running openshift-install in pod containers, and we're seeing failure there but success running the container manually with the exact same image. Please hold on any major investigation. |
Yeah, the cluster-network-operator is a very special snowflake. It is run before the bootstrap apiserver is torn down. That means it's running on the masters, talking to the boostrap control plane. In some sense, it's the canary in the coal mine. |
I've not seen any major issues with the openshift-sdn for a while; closing this. If you see more issues please open another bug. |
Yeah this was on our end. Thanks! |
Multiple folks on our team are seeing this today.
Using an image built from: openshift/installer@08018ca
We end up completing install, mostly:
Masters are permanently stuck notready:
Their status contains a condition like:
With a similar error in the kubelet systemd logs:
cluster-network-operator pod logs show:
The text was updated successfully, but these errors were encountered: