Bug 712195 - remove 'ext4migrate' option
Summary: remove 'ext4migrate' option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Cantrell
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-09 18:42 UTC by David Cantrell
Modified: 2011-12-06 10:38 UTC (History)
6 users (show)

Fixed In Version: anaconda-13.21.120-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:38:07 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1565 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-12-06 00:39:12 UTC

Description David Cantrell 2011-06-09 18:42:39 UTC
Use of the ext4migrate option results in unsupported ext4 filesystems.  Product management and GSS have requested that we remove the ability to migrate ext3 filesystems to ext4 in anaconda.

Comment 1 RHEL Program Management 2011-06-09 19:00:07 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has 
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed 
products. This request is not yet committed for inclusion in an Update release.

Comment 4 Alexander Todorov 2011-08-04 15:15:07 UTC
I tested this with anaconda-13.21.125-1 doing an upgrade from 6.0 with ext3 partitions to 6.2. Upgrade completed, no traceback and fstype not changed.

Comment 5 errata-xmlrpc 2011-12-06 10:38:07 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2011-1565.html


Note You need to log in before you can comment on or make changes to this bug.