Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add unit to drop to emergency shell after a timeout if still in initramfs #796

Open
dustymabe opened this issue Apr 16, 2021 · 2 comments
Open

Comments

@dustymabe
Copy link
Member

There are a few things that will wait forever for a remote resource to exist before continuing. One of them is the pxe rootfs downloading (coreos/fedora-coreos-config#964) the other is Ignition trying to fetch a remote Ignition config.

Sometimes it's useful to break out of the failure and debug the environment. Maybe we could add a systemd unit that would takek an argument for a timeout and if that timeout is reached then we break into the emergency shell.

Something like rd.coreos.emergency.timeout=600. If that option doesn't exist the unit doesn't run. If it does it runs sleep 600 and then drops to emergency shell

A counter argument to a feature like this is to just have someone add a rd.break argument and debug that way. Thought I could see a user choosing to always put rd.coreos.emergency.timeout=600 on the kernel command line to just get to an emergency shell automatically any time things are taking longer than X amount of time.

@travier
Copy link
Member

travier commented Apr 28, 2021

We discussed that in the community meeting today.

We agreed initially to make it first boot only but might reconsider to enable it for all boots given that we don't really have a good threat model where this would be worse than the current status:

* AGREED: we think having a generic configurable timeout via a kernel
argument to break if things wait infinitely would be useful. We just
want to make sure that it's not on by default and that it only
applies to the first boot of a machine. (dustymabe, 17:21:16)

Related console access issue: #805

@jlebon
Copy link
Member

jlebon commented Aug 25, 2021

Related: #928

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants