Hi, According to the link https://coreos.com/ignition/docs/latest/boot-process.html, ignition only takes effect at the first boot. But we want to make it effect later if we missed something in the first boot, or we want to debug ignition. So question is: how can I set file coreos/first_boot in the EFI System Partition, or set 'coreos.first_boot=detected' in kernel parameter line in an existing coreos qcow2 image which can be started, so that I can make ignition work?
Thanks a lot!
On Tue, Jun 4, 2019 at 8:13 AM QingFeng Hao haoqf@linux.vnet.ibm.com wrote:
Hi, According to the link https://coreos.com/ignition/docs/latest/boot-process.html, ignition only takes effect at the first boot. But we want to make it effect later if we missed something in the first boot, or we want to debug ignition.
If you missed something, it's safer to just fix your Ignition config and reprovision the machine from scratch. Ignition has non-idempotent bits in it, for example the `append` and `overwrite` keys.
That said, if you really do want to have Ignition rerun for debugging purposes, in FCOS/RHCOS you can use `ignition.firstboot=1`. This gets picked up here: https://github.com/coreos/ignition-dracut/blob/df88988f2f0791ca9ea1e14298c85...
The docs at https://coreos.com/ are generally for Container Linux, though some things do apply to RHCOS/FCOS (e.g. the Ignition v2.2 specification for RHCOS). I don't think we have this specific change documented somewhere else yet.
Thanks a lot!
-- Regards QingFeng Hao _______________________________________________ CoreOS mailing list -- coreos@lists.fedoraproject.org To unsubscribe send an email to coreos-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
在 2019/6/4 21:19, Jonathan Lebon 写道:
On Tue, Jun 4, 2019 at 8:13 AM QingFeng Hao haoqf@linux.vnet.ibm.com wrote:
Hi, According to the link https://coreos.com/ignition/docs/latest/boot-process.html, ignition only takes effect at the first boot. But we want to make it effect later if we missed something in the first boot, or we want to debug ignition.
If you missed something, it's safer to just fix your Ignition config and reprovision the machine from scratch. Ignition has non-idempotent bits in it, for example the `append` and `overwrite` keys.
That said, if you really do want to have Ignition rerun for debugging purposes, in FCOS/RHCOS you can use `ignition.firstboot=1`. This gets picked up here: https://github.com/coreos/ignition-dracut/blob/df88988f2f0791ca9ea1e14298c85...
Thanks a lot! The problem is: I can't find the place to change the kernel cmdline in coreos VM. No grub, zipl.conf or other config at all. Do you know where I can change it? Thanks!
The docs at https://coreos.com/ are generally for Container Linux, though some things do apply to RHCOS/FCOS (e.g. the Ignition v2.2 specification for RHCOS). I don't think we have this specific change documented somewhere else yet.
Thanks a lot!
-- Regards QingFeng Hao _______________________________________________ CoreOS mailing list -- coreos@lists.fedoraproject.org To unsubscribe send an email to coreos-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
CoreOS mailing list -- coreos@lists.fedoraproject.org To unsubscribe send an email to coreos-leave@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/coreos@lists.fedoraproject.org
coreos@lists.fedoraproject.org
-
Jonathan Lebon -
QingFeng Hao