Skip to content
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.

Sign up for GitHub

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

Jump to bottom

csr approval can fail if cluster is slow to startup #903

Closed
cfergeau opened this issue Dec 19, 2019 · 0 comments
Closed

csr approval can fail if cluster is slow to startup #903

cfergeau opened this issue Dec 19, 2019 · 0 comments

Comments

@cfergeau
Copy link
Contributor

If the cluster is on a slow machine, 3 minutes may not be enough for the CSR
resource to become available. We can make use of the new waitForOpenshiftAPIServer
to avoid failures if it's not available yet.
cfergeau added a commit to cfergeau/crc that referenced this issue Dec 19, 2019
@cfergeau
Issue crc-org#903: Move waitForOpenshiftAPIServer from cluster to oc
d4fe4c2 
Since it only needs to be able to run 'oc', this can be moved to the oc
package.
cfergeau added a commit to cfergeau/crc that referenced this issue Dec 19, 2019
@cfergeau
Issue crc-org#903: Wait for csr resource before trying to approve the…
052d052 
… CSRs

When the cluster is particularly slow to startup, we may try to approve
the CSRs before the corresponding resource is available. Now that we
have a WaitForOpenshiftResource method, we can make use of it for the
CSRs as well.

This fixes crc-org#903
praveenkumar pushed a commit that referenced this issue Dec 20, 2019
@cfergeau @praveenkumar
Issue #903: Move waitForOpenshiftAPIServer from cluster to oc
0eba661 
Since it only needs to be able to run 'oc', this can be moved to the oc
package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cfergeau