-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
馃尡 Add BootstrapFailedMachineError error #10360
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/area machine |
/ok-to-test |
// indicates a state that must be fixed before progress can be made. | ||
// | ||
// Example: the ControlPlaneEndpoint is wrong. | ||
BootstrapFailedMachineError MachineStatusError = "BootstrapFailed" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do we make sure that users don't confuse this with that the bootstrap provider failed?
(edited)
@mcbenjemaa this would be very useful. These kind of errors though might happen after the iaas considers an instance started, in which case they are not surfaced/exposed in any immediate consumable way. Can you articulate an example of how such a failure would be detected and bubble up here? To make sure we approach this holistically and come up with the most valuable approach, we might want to start by writing down some failure scenarios and how they would be surfaced. |
I'm Using CAPI provider for Proxmox, With Proxmox im calling the API to check the status of cloud-init. And based on that, will mark a machine as Bootstrap Failed, |
What this PR does / why we need it:
In some infra providers, we need more configuration to provision a cluster.
For example, cloud-init config and control plane endpoint.
Since there are no validations for those configs, the Bootstrap (cloud-init) may fail due to misconfiguration, and we need to figure out why.
Having a new machine error reason will give clear idea what's happening to users
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
/area machine