[Bug 1185461] New: ignition doesn't reset firstboot
http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 Bug ID: 1185461 Summary: ignition doesn't reset firstboot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: lnussel@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Using openSUSE-MicroOS.x86_64-16.0.0-kvm-and-xen-Snapshot20210427.qcow2 in qemu with an ignition config that touches a file in /etc. Rebooting leads to maintenance mode as ignition started again and exists as the file already exist. So for some reason the no firstboot condition is not detected. /boot/writable/firstboot_happened exist though: Entering emergency mode. Exit the shell to continue. Type "journalctl" to view system logs. You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot after mounting them and attach it to a bug report. Press Enter for maintenance (or press Control-D to continue): :/root# mount -o subvol=@/boot/writable /dev/vda3 /mnt :/root# ls /mnt/ firstboot_happened :/root# cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.11.16-1-default root=UUID=1bd1020f-74e9-4d1f-bb36-859e1f4e86bd rw rd.timeout=60 quiet systemd.show_status=yes console=ttyS0,115200 console=tty0 net.ifnames=0 ignition.firstboot ignition.platform.id=qemu -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 http://bugzilla.opensuse.org/show_bug.cgi?id=1185461#c1 --- Comment #1 from Ludwig Nussel <lnussel@suse.com> --- Created attachment 848886 --> http://bugzilla.opensuse.org/attachment.cgi?id=848886&action=edit ignition config -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 http://bugzilla.opensuse.org/show_bug.cgi?id=1185461#c2 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iforster@suse.com, | |lnussel@suse.com Flags| |needinfo?(lnussel@suse.com) --- Comment #2 from Ignaz Forster <iforster@suse.com> --- Unfortunately I can't reproduce this problem here. Such a behavior would indicate that GRUB wasn't able to find /boot/writable/firstboot_happened / failed to mount /boot/writable. If you can still reproduce this: Would it be possible to check whether the file is also visible from within GRUB? -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 http://bugzilla.opensuse.org/show_bug.cgi?id=1185461#c3 --- Comment #3 from Ignaz Forster <iforster@suse.com> --- I'm wondering: Would it have been possible that the image file itself was updated while the virtual machine was running? I've seen similar strange symptoms when the cronjob on future updated the corresponding image via rsync in the background (which it seems to do quite often these days). -- You are receiving this mail because: You are the assignee for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185461 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|kubic-bugs@opensuse.org |iforster@suse.com -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com