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
{{ message }}
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.
When Ignition is fed a bad config, it prevents the boot from succeeding. As a result, the packet-phone-home.service doesn't run, which leaves the machine in a failed provisioning state (Packet then removes the machine from the available pool). Instead, packet-phone-home.service should be run from the initramfs when Ignition fails. This will allow Packet to continue using that machine and the user to get a console and debug.
Other Information
It would be nice if the API allowed us to indicate a boot failure, but I don't believe it supports that yet.
The text was updated successfully, but these errors were encountered:
Issue Report
Feature Request
Environment
Packet.net
Desired Feature
When Ignition is fed a bad config, it prevents the boot from succeeding. As a result, the
packet-phone-home.service
doesn't run, which leaves the machine in a failed provisioning state (Packet then removes the machine from the available pool). Instead,packet-phone-home.service
should be run from the initramfs when Ignition fails. This will allow Packet to continue using that machine and the user to get a console and debug.Other Information
It would be nice if the API allowed us to indicate a boot failure, but I don't believe it supports that yet.
The text was updated successfully, but these errors were encountered: