[Bug 1893428] New: netinstall image requirement for using kickstart
could be made clearer
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1893428
Bug ID: 1893428
Summary: netinstall image requirement for using kickstart could
be made clearer
Product: Fedora Documentation
Version: devel
Status: NEW
Component: install-guide
Severity: low
Assignee: pbokoc(a)redhat.com
Reporter: glaebhoerl(a)gmail.com
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: pbokoc(a)redhat.com, zach(a)oglesby.co
Target Milestone: ---
Classification: Fedora
Based on the
https://docs.fedoraproject.org/en-US/fedora/f33/install-guide/advanced/Ki...
page, I attempted to add an inst.ks= boot option to my Fedora Workstation
installation image (after copying its contents to a FAT32 filesystem). This
resulted, when beginning the installation, in the message:
"Kickstart is not supported on live installs. This installation will continue
interactively."
Googling for this message found single-digit hits, almost all of which were for
the several-years-old commit which originally added the message.
It was very unclear to me what I should have been doing instead, and spent most
of a day fruitlessly googling to try to find out. Every page only ever said
that I needed to add a boot option to the kernel command line of the installer
(which is what I believed myself to be doing), and went from there. The root of
the issue is that it was not apparent to me what the alternative to a "live
install" was, or how to activate it. (Maybe I needed to pass different boot
options so that it would boot directly into the installer?? I spent a while
trying different ways to achieve this.)
"Kickstart is not supported on live installs" may have been sufficient
information back in the day when live and non-live installation images were
provided side by side, but these days, at least for the Workstation version,
live is the only download option prominently visible, and it is not even called
out as being such.
Finally, after trying the twentieth combination of search terms, I found that
the page
https://docs.fedoraproject.org/en-US/fedora/f33/install-guide/install/Pre...
mentions that "Kickstart installation requires the netinstall media type, or a
direct installation booting method such as PXE; kickstarts are not supported
with live images". I admit that if I had read all of the instructions linearly
from beginning to end, then I would probably not have had this problem.
Nonetheless, I humbly suggest that if the "Automating the Installation with
Kickstart" page also made some mention of this requirement, it would be a
helpful thing. In addition, it might be helpful to extend the "kickstart is not
supported on live installs" error message with some mention of the suggested
alternatives as well.
Thank you for your work and attention.
--
You are receiving this mail because:
You are the QA Contact for the bug.
2 years, 10 months
[Bug 1889931] New: feature request: release notes document status of
systemd-homed for install and upgrade to fedora33
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=1889931
Bug ID: 1889931
Summary: feature request: release notes document status of
systemd-homed for install and upgrade to fedora33
Product: Fedora Documentation
Version: devel
OS: Linux
Status: NEW
Component: release-notes
Severity: medium
Assignee: pbokoc(a)redhat.com
Reporter: william.garber(a)att.net
QA Contact: docs-qa(a)lists.fedoraproject.org
CC: relnotes(a)fedoraproject.org, wb8rcr(a)arrl.net,
zach(a)oglesby.co
Target Milestone: ---
Classification: Fedora
Description of problem:
would like some easy to find documentation on status of systemd-homed setup
for install and/or upgrade to fedora33.
i.e. what happens to standard home directory on upgrade.
Version-Release number of selected component (if applicable):
fedora 32 upgrade to fedora 33
How reproducible:
would like to know how this works before installing.
Additional info:
was not so easy to find on web.
should be more easy to find on fedora website.
--
You are receiving this mail because:
You are the QA Contact for the bug.
3 years, 6 months