Bug 695362

Summary: Selected filesystem is changed to ext4 for /boot partition
Product: Red Hat Enterprise Linux 6 Reporter: Jan Stodola <jstodola>
Component: anacondaAssignee: David Lehman <dlehman>
Status: CLOSED ERRATA QA Contact: Release Test Team <release-test-team>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: atodorov
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-13.21.119-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-06 10:32:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 670159, 705163    
Attachments:
Description Flags
storage.log none

Description Jan Stodola 2011-04-11 13:40:36 UTC 
Description of problem:
When creating /boot partition, anaconda always changes selected file system to ext4, see steps to reproduce.

Version-Release number of selected component (if applicable):
RHEL6.1-20110406.0
anaconda-13.21.111-1.el6

How reproducible:
always

Steps to Reproduce:
1. run graphical installation
2. use custom partitioning
3. remove existing partitions
4. Create -> Standard Partition -> Create
5. File System Type: ext3
6. Mount Point: /boot
  
Actual results:
File system is changed to ext4

Expected results:
File system remains ext3
Comment 1 Chris Lumens 2011-04-15 02:25:36 UTC 
Please attach /tmp/storage.log to this bug report.  Thanks.
Comment 2 Jan Stodola 2011-04-15 08:46:52 UTC 
Created attachment 492306 [details]
storage.log

1. start anaconda with all drives formatted
2. select custom partitioning
3. create new partition:
 a) set FS Type: ext3
 b) set mount point: /boot
 c) anaconda changes FS Type to ext4
4. copy storage.log...
Comment 6 Alexander Todorov 2011-08-04 15:31:50 UTC 
Tested with anaconda-13.21.125 and fstype is not changed when /boot mount point is selected.
Comment 7 errata-xmlrpc 2011-12-06 10:32:12 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