Bug 1040422
| Summary: | Standard partitions can't be enlarged | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Kamil Páral <kparal> | ||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 20 | CC: | anaconda-maint-list, atorkhov, dshea, g.kaviyarasu, jonathan, mruckman, robatino, vanmeeuwen+fedora | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | Unspecified | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | RejectedBlocker | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2014-03-07 18:54:23 UTC | Type: | Bug | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Kamil Páral
2013-12-11 12:10:59 UTC
Created attachment 835241 [details]
anaconda.log
Created attachment 835242 [details]
program.log
Created attachment 835243 [details]
storage.log
Created attachment 835244 [details]
syslog
Proposing a Final blocker: "Any installer mechanism for resizing storage volumes must correctly attempt the requested operation. " https://fedoraproject.org/wiki/Fedora_20_Final_Release_Criteria#Storage_volume_resize Does it have free space right after /boot in such case? If not it needs to relocate PV partition which is not supported, I guess. Discussed in 2013-12-11 Blocker Review Meeting [1]. Voted as an RejectedBlocker. This is probably a UI issue failing to inform the user properly what can and what cannot be achieved. It's not possible to redesign UI to fix this in a short time. If this really affects real cases where there is enough contiguous space for resize, please propose again. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-12-11/ Confirming the assessment of comment 7: /boot cannot be enlarged because there's nowhere to enlarge it into: the pv starts on the next sector. anaconda will not move existing partitions. How is the user supposed to know that something starts on the next sector, when you don't offer any graphical layout representation? On the one hand, you try to offer a dumbed-down partitioning editor for users with no advanced knowledge in this area, but on the other hand in certain cases you simply reject an operation based on something the users couldn't have possibly known, even if they were partitioning gurus, because you decide to not provide this information in the first place. This is not a NOTABUG. This is a bug, a design flaw, just different from the original description. |