[Bug 1176566] New: Installing ignition leads to unbootable system
http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 Bug ID: 1176566 Summary: Installing ignition leads to unbootable system Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Critical Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: rombert@apache.org QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I've installed ignition locally on Tumbleweed, to be able to validate ignition files locally. After a reboot I was presented with an emergency shell, leading down a wild goose chase for disabling ignition permanently. It all went away after setting up a chroot and removing all traces of ignition, but it would be much much better if installing it would not lead to a broken system by default. I saw some errors related to the ignition generator, and the systemd unit file was broken, but could not save any logs unfortunately. But it should be easy enough to reproduce if anyone cares: # zypper in ignition # reboot (Might be related to #1172592) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |iforster@suse.com Assignee|kubic-bugs@opensuse.org |iforster@suse.com -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 http://bugzilla.opensuse.org/show_bug.cgi?id=1176566#c1 Joed L <jlopez777+opensuse@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jlopez777+opensuse@gmail.co | |m, rombert@apache.org Flags| |needinfo?(rombert@apache.or | |g) --- Comment #1 from Joed L <jlopez777+opensuse@gmail.com> --- Its been some time, can you try again and update accordingly? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 http://bugzilla.opensuse.org/show_bug.cgi?id=1176566#c2 --- Comment #2 from Robert Munteanu <rombert@apache.org> --- Sorry, I don't have time right now to validate if installing ignition locally will bork my system again :-) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1176566 http://bugzilla.opensuse.org/show_bug.cgi?id=1176566#c3 Ignaz Forster <iforster@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME Flags|needinfo?(rombert@apache.or | |g) | --- Comment #3 from Ignaz Forster <iforster@suse.com> --- 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). -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com