Bug 232936
| Summary: | Partitions not being created in raid install | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Orion Poplawski <orion> | ||||
| Component: | anaconda | Assignee: | Chris Lumens <clumens> | ||||
| Status: | CLOSED RAWHIDE | QA Contact: | |||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | rawhide | CC: | smagoun | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2007-04-23 20:14:47 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: | 150226 | ||||||
| Attachments: |
|
||||||
|
Description
Orion Poplawski
2007-03-19 15:32:09 UTC
Created attachment 150379 [details]
anaconda dump
Still happens with 11.2.0.39. This strikes me as a pretty serious failure. Can anyone else reproduce? I can confirm this. I'm going to try a kickstart without lvm to see if its specifically lvm causing the problem. I've seen errors when just creating basic configs on a single IDE drive, no LVM anywhere in the config, (1 GB swap, the rest being / and ext3) on T2 ... tried dd'ing the drive before to clean it off, still no good. I spoke briefly with jeremy on #et-mgmt and he seemed to imply LVM was at fault. This happens when using kickstart or not. To clarify, no lvm was involved, but the lvm still choked on my setup while looking for partitions. I don't exactly remember the details as I do not have the machine around anymore but can help recreate if needed. *** Bug 232502 has been marked as a duplicate of this bug. *** The problem here is that we're executing the clearpart code at least twice, and one of those times is after we've committed the partitions to disk. If you use existing partitions or dd in your %pre script to clear out the disk label, you should be able to work around this problem. Of course, it's still a bug. I'm not sure why this is only showing up as a bug now, and it's a bit of a tangle of code to work through. I have a preliminary patch worked up for testing here. Committed a potential fix for this issue, though the risk of regressions when editing this stuff is always pretty high. I'll put it in MODIFIED for now. Please test the next build of anaconda and if this issue is solved, we'll close it out. Thanks. |