Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
grub.cfg is empty after installation (using RHEL6.3-20120313.2)
Version-Release number of selected component (if applicable):
anaconda-13.21.161-1.el6.x86_64
shipped with RHEL6.3-20120313.2
How reproducible:
2 / 2
Steps to Reproduce:
1. perform an url installation, ks will be attached. (here i am installing a kvm guest)
2./home/autotest-devel/client/tests/kvm/qemu -name 'vm1' -nodefaults -vga std -chardev socket,id=qmp_monitor_id_qmpmonitor1,path=/tmp/monitor-qmpmonitor1-20120327-145238-Kpwk,server,nowait -mon chardev=qmp_monitor_id_qmpmonitor1,mode=control -chardev socket,id=serial_id_20120327-145238-Kpwk,path=/tmp/serial-20120327-145238-Kpwk,server,nowait -device isa-serial,chardev=serial_id_20120327-145238-Kpwk -device ich9-usb-uhci1,id=usb1,bus=pci.0,addr=0x4 -drive file='/home/autotest-devel/client/tests/kvm/images/RHEL-Server-6.3-64-virtio.qcow2',index=0,if=none,id=drive-virtio-disk1,media=disk,cache=none,boot=off,snapshot=off,readonly=off,format=qcow2,aio=native -device virtio-blk-pci,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -device virtio-net-pci,netdev=id8Jw46f,mac=9a:e5:b9:fa:eb:19,id=ndev00id8Jw46f,bus=pci.0,addr=0x3 -netdev tap,id=id8Jw46f,vhost=on,fd=21 -m 16384 -smp 4,cores=2,threads=1,sockets=2 -cpu 'Conroe' -drive file='/home/autotest-devel/client/tests/kvm/images/rhel63-64/ks.iso',index=2,if=none,id=drive-ide0-0-0,media=cdrom,boot=off,snapshot=off,readonly=on,format=raw -device ide-drive,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0 -device usb-tablet,id=usb-tablet1,bus=usb1.0 -kernel '/home/autotest-devel/client/tests/kvm/images/rhel63-64/vmlinuz' -append 'ks=cdrom nicdelay=60 console=ttyS0,115200 console=tty0' -initrd '/home/autotest-devel/client/tests/kvm/images/rhel63-64/initrd.img' -spice port=8000,disable-ticketing -vga qxl -rtc base=utc,clock=host,driftfix=slew -M rhel6.3.0 -boot order=cdn,once=d,menu=off -no-kvm-pit-reinjection -no-shutdown -enable-kvm
3.
Actual results:
guest unable to boot, need to point out the kernel/initramfs path.
Expected results:
guest boot without needing type in kernel/initramfs path manually.
Additional info:
host is installed using same tree, no such issue.
Created attachment 573225[details]
tar xf log.tar
it's not always reproducible, guest able to boot this time.
Comment 7RHEL Program Management
2012-05-03 05:11:33 UTC
Since RHEL 6.3 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.