Red Hat Bugzilla – Bug 157201
When doing a text-mode kick-start install the command "lvm vgchange -a y" is not run for LVM volumes
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.4; Linux) KHTML/3.4.0 (like Gecko)
Description of problem:
I have a kickstart config to install Fedora on LVM volumes. In GUI mode
things work fine. In text mode it attempts to run mkfs without first running
"lvm vgchange -a y" to create the /dev/mapper nodes, this causes the install
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Try to do a kickstart install onto LVM logical volumes in text mode. Observe
that the same install works in GUI mode but not in text mode.
My initial report lacked an important detail.
I tried the install again with running "lvm vgchange -a y" from the console
(VT2) at the appropriate time. All needed /dev/mapper entries were created.
Then sometime during the step "moving (1) to step enablefilesystems"
the /dev/mapper entries were removed, possibly at the stage of "formatting
None as volume group (LVM)" or "formatting None as physical volume (LVM)".
Text vs GUI should be identical as far as this is concerned (all of the steps
which do any of this activation are independent of the UI). Please provide the
error from when it failed.
I've put pictures of the screen on http://www.coker.com.au/bug/anaconda/ .
Also note that the problem doesn't seem to occur on a machine with 256M of
RAM, but occurs on machines with 64M of RAM.
Can you attach your ks.cfg ?
Created attachment 114446 [details]
Can you also provide /tmp/anaconda.log and /tmp/syslog?
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product. If you have further details, feel free to
reopen the report with the additional details attached.