What | Removed | Added |
---|---|---|
Status | NEW | RESOLVED |
Resolution | --- | WORKSFORME |
Flags | needinfo?(rombert@apache.org) |
I can't reproduce the behavior here (but I also couldn't back when the ticket was opened). Shortly after the ticket was opened the trigger mechanism was changed from deleting a maker file to the current "create /boot/writable/firstboot_happened on first successful boot" mechanism, so this may have had an influence, too. In any case: Ignition *should* just apply an empty configuration when no configuration file could be found anywhere (apart from some rare provider implementations which will time out with an error, but those would have to be configured by the user manually). I'll close this ticket for now, but please reopen if anybody should see it again (and append the log file).