-
Notifications
You must be signed in to change notification settings - Fork 79
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
If transit gateway fails creation in PowerVS then fail CAPI deploy #1653
Comments
@hamzy thanks for reporting an issue, can you please dump more information like complete dump of the @Karthik-K-N are we setting right state for the cluster when error happens? This needs discussion how to fail fast when things go wrong! at least we need have some condition or design how many times do we really want to retry if something gets failed to create |
|
@hamzy as we can see that condition in the status for the Considering the way controllers designed it always looks for making that resource available even after the failure in the next retry. Its user's concise decision when to terminate the cluster based on the conditions or go and fix the environment in the backend to proceed the installation flow(e.g: user talking to admin to bump the limit for the transit gateways in this case) May be having a timeout in the installer with some level of error checking of these conditions will be a better way to deal with such situations. |
as per above comment closing this issue |
/kind bug
/area provider/ibmcloud
What steps did you take and what happened:
[A clear and concise description of what the bug is.]
During an IPI CAPI create cluster, a transit gateway is not created. The cluster is useless without this.
What did you expect to happen:
Immediate failure.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:
kubectl version
):/etc/os-release
):The text was updated successfully, but these errors were encountered: