You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
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.
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"
The text was updated successfully, but these errors were encountered: