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
Afterburn usually follows Ignition platform naming convention, in order to auto-detect the platform.
However there are several platforms where the metadata component is only optional. On those platforms, in case of failures, Afterburn cannot distinguish a known-good state (i.e. this infra lacks the metadata component) from a failed state (i.e. network or logic error).
As such, Afterburn knows about the following platform which are more specific than the Ignition ones, cannot be auto-detected, and require user-provided hints (as cmdline flags):
cloudstack-metadata
cloudstack-configdrive
openstack-metadata
vagrant-virtualbox
The text was updated successfully, but these errors were encountered:
openstack-metadata has since been consolidated into a platform ID openstack that does match Ignition. vagrant-virtualbox has been removed, and #856 tracks consolidation of the CloudStack providers into a cloudstack one. Closing this in favor of fixing CloudStack to use the Ignition platform ID.
Afterburn usually follows Ignition platform naming convention, in order to auto-detect the platform.
However there are several platforms where the metadata component is only optional. On those platforms, in case of failures, Afterburn cannot distinguish a known-good state (i.e. this infra lacks the metadata component) from a failed state (i.e. network or logic error).
As such, Afterburn knows about the following platform which are more specific than the Ignition ones, cannot be auto-detected, and require user-provided hints (as cmdline flags):
cloudstack-metadata
cloudstack-configdrive
openstack-metadata
vagrant-virtualbox
The text was updated successfully, but these errors were encountered: