Bug 683873
| Summary: | --onpart/--ondisk doesn't work - could not allocate requested partitions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> | ||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Release Test Team <release-test-team-automation> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | high | ||||||||||||
| Version: | 6.1 | ||||||||||||
| Target Milestone: | rc | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2011-03-10 15:37:39 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Bug Depends On: | |||||||||||||
| Bug Blocks: | 621515, 670159 | ||||||||||||
| Attachments: |
|
||||||||||||
Created attachment 483472 [details]
program.log
Created attachment 483473 [details]
storage.log
Created attachment 483474 [details]
syslog
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.