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.
DescriptionAlexander Todorov
2011-03-10 14:55:09 UTC
Created attachment 483471[details]
anaconda.log
Description of problem:
When trying to reprovision a RHEL6.1 system using the --onpart/--ondisk parameters I get an error and install stops.
Version-Release number of selected component (if applicable):
anaconda-13.21.104-1.el6.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Install a KVM domU with 2 virtio disks where /boot, swap and / are on vda1 and /mydata on vda2. Write down the symlinks in /dev/disk/by-path.
2. Reinstall the same system using ks.cfg:
bootloader --location=mbr
clearpart --none
part /boot --fstype=ext4 --size=1024 --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1
part swap --size=1024 --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1
part / --fstype=ext4 --size=500 --grow --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1
part /mydata --fstype=ext4 --onpart=/dev/disk/by-path/pci-0000:00:06.0-virtio-pci-virtio2-part1 --noformat --size=500 --grow
3.
Actual results:
An error - Could not allocate requested partitions.
Expected results:
System is reinstalled. /mydata is intact.
Additional info:
See attached log files.
Comment 1Alexander Todorov
2011-03-10 14:55:40 UTC
Your vda is completely full of partitions. You specify clearpart --none and then proceed to try to allocate three partitions on the same (full) disk of sizes 500, 1024, 1024. Of course it fails.
Created attachment 483471 [details] anaconda.log Description of problem: When trying to reprovision a RHEL6.1 system using the --onpart/--ondisk parameters I get an error and install stops. Version-Release number of selected component (if applicable): anaconda-13.21.104-1.el6.x86_64 How reproducible: Always Steps to Reproduce: 1. Install a KVM domU with 2 virtio disks where /boot, swap and / are on vda1 and /mydata on vda2. Write down the symlinks in /dev/disk/by-path. 2. Reinstall the same system using ks.cfg: bootloader --location=mbr clearpart --none part /boot --fstype=ext4 --size=1024 --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1 part swap --size=1024 --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1 part / --fstype=ext4 --size=500 --grow --ondisk=/dev/disk/by-path/pci-0000:00:05.0-virtio-pci-virtio1 part /mydata --fstype=ext4 --onpart=/dev/disk/by-path/pci-0000:00:06.0-virtio-pci-virtio2-part1 --noformat --size=500 --grow 3. Actual results: An error - Could not allocate requested partitions. Expected results: System is reinstalled. /mydata is intact. Additional info: See attached log files.