-
Notifications
You must be signed in to change notification settings - Fork 50
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
Unattended ISO should not auto-reboot #230
Labels
Comments
cgwalters
added
bug
Something isn't working
area/anaconda-iso
Issues relating to the unattended Anaconda ISO
labels
Mar 4, 2024
@cgwalters ran into this issue earlier where after doing an unattended download it would forever reboot and my server would do a loud BEEP and reboot again.. Thought it had finished installing, but nope. Would like to have this feature in as it'll help with installs on monitor-less servers! |
mvo5
added a commit
to mvo5/images
that referenced
this issue
May 27, 2024
In issue osbuild#230 it was raised that it is undesirable to automatically reboot when the install is finished. So instead halt the install and show a message to the user. Closes: osbuild/bootc-image-builder#230
mvo5
added a commit
to mvo5/bootc-image-builder
that referenced
this issue
May 27, 2024
The old images code would auto-reboot after an ISO install so the test code triggered on qmp:RESET. However with the change to not auto-reboot [0] this is no longer feasible and we need to detect `DEVICE_TRAY_MOVED` events that are emited when kickstart calls `halt --eject`. [0] osbuild#230
mvo5
added a commit
to mvo5/images
that referenced
this issue
May 27, 2024
In issue osbuild#230 it was raised that it is undesirable to automatically reboot when the install is finished. So instead halt the install and show a message to the user. Closes: osbuild/bootc-image-builder#230
Thanks for this bugreport. I was looking into this morning and two questions came up:
|
For virtualized testing I think anaconda should default to sending success/failure over a virtio serial/vsock. Writing success can easily be done in a %post.
For the bare metal case maybe anaconda could learn to special case things so that only trying to reinstall the exact same OS version errors out by default?
|
mvo5
added a commit
to mvo5/images
that referenced
this issue
Aug 1, 2024
In issue osbuild#230 it was raised that it is undesirable to automatically reboot when the install is finished. So instead halt the install and show a message to the user. Closes: osbuild/bootc-image-builder#230
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
https://github.com/osbuild/images/blob/32bd652a96b5cc3ebb0066c29a2086fd6ce48913/pkg/manifest/anaconda_installer_iso_tree.go#L452 will create a boot loop when used with an ISO dd'd to a USB stick (this is really the default, I doubt anyone uses physical ISOs in real CD-ROM drives anymore) because we can't "eject" the USB key.
This is also part of a general problem that the kickstart has zero configurability.
The text was updated successfully, but these errors were encountered: