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.

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

More specific error message as part of CAPOCI events when there are no IPs available to be attached on the new node. #360

Open
pulgarg opened this issue Mar 19, 2024 · 1 comment
Labels
enhancement New feature or request

Comments

@pulgarg
Copy link

pulgarg commented Mar 19, 2024

What would you like to be added:
we would like to have support for specific error messages to be available in CAPOCI events when there are no IPs available to be attached to the instance being provisioned. We want the message to come from compute workrequest instead of a generic message.

Why is this needed:
A message similar to "No more available IP in CIDR 10.0.10.0/24" coming from the compute workrequest would give a better idea about the issue than what we are getting right now as part of CAPOCI events, ie. "oke-7c6a84abe44f43f5a7bafd13c32d8f3d-qstlg.17a3b3bdfd981416: Instance has invalid lifecycle state TERMINATING"

@pulgarg pulgarg added the enhancement New feature or request label Mar 19, 2024
@pulgarg
Copy link
Author

pulgarg commented Mar 20, 2024

A similar case is there when cluster create fails because there are no IPs available for NLB to be created. It would be better if the message we get in the CAPOCI events could be enhanced and could come from network load balancer workrequest error saying something like "No more available IP in CIDR 172.31.252.240/28", instead of "Failed to create cluster due to an Unknown error" which we are getting currently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant