-
Notifications
You must be signed in to change notification settings - Fork 246
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
Add ability for Ignition to report provisioning failures #592
Comments
Comment by @bgilbert See also coreos/bugs#2042, coreos/bugs#2130. |
Comment by @Bubblemelon In reference to https://www.packet.net/developers/api/devices/ by using a Packet Token and a Instance ID:
The above is reflected on the "Timeline" tab of the "kola-6784...bd2a" server instance deployed through My Question is: If I have tried running different OS servers just to see the difference in the Timeline and what the JSON field for Second Question: What Type should the Status property be in the Config struct of |
Comment by @dgonyeo For those following along at home, I talked to Cheryl in person and was able to answer her questions |
Fixed in the general case by #566. If we want to support more clouds we should open cloud specific bugs for them. |
Issue by @dgonyeo
Issue Report
Feature Request
Environment
All
Desired Feature
Some clouds (ex: packet.net provide the ability for a machine to report their state. Once Ignition fails, it should report this state to the cloud it's running on.
Other Information
internal/providers
provides cloud-specific logic. An additional function could be added there that gets called when Ignition fails (pretty much identically to how theNewFetcher
function there gets used). Packet seems like a good first choice for a cloud to do this on.#585 is related, but that suggests reporting to a user-provided URL whereas this is reporting to the APIs for the given cloud environment in which Ignition is running.
The text was updated successfully, but these errors were encountered: