Bug 626826
Summary: | Anaconda fails to grow a partition using a custom partition-include | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Mathieu Chouquet-Stringer <mathieu-acct> |
Component: | doc-Migration_Guide | Assignee: | Laura Bailey <lbailey> |
Status: | CLOSED NEXTRELEASE | QA Contact: | ecs-bugs |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | Keywords: | Documentation |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-08-24 22:30:51 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: |
Description
Mathieu Chouquet-Stringer
2010-08-24 14:12:08 UTC
You can't use "--size=1 --grow" anymore. You need to give those partitions a reasonable default size given that you are building multiple layers of things on top of them. If you change that, does that cause this issue to go away? Duly noted, if I specify a reasonable default size, partitions are grown accordingly... I guess it should be in the docs... So yes, the issue goes away. added to migration guide in kickstart section |