Bug 743441 - Cannot customise root filesystem type
Summary: Cannot customise root filesystem type
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: scheduler
Version: 0.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: Dan Callaghan
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-04 23:10 UTC by Dan Callaghan
Modified: 2019-05-22 13:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-06 04:40:18 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Dan Callaghan 2011-10-04 23:10:27 UTC 
Beaker does not provide any way to change the filesystem type used for the root and boot filesystems.

The other problem here is that on RHEL6 the default should be ext4 (that's what anaconda uses if Beaker specifies autopart) but if the job has custom partitions the root and boot filesystems will always be ext3 instead.
Comment 1 Dan Callaghan 2011-10-04 23:11:04 UTC 
The snippet in question is rhts_partitions. If the partitions variable (corresponds to <partitions/> in job xml) or the ondisk variable are not set, Beaker just spits out "autopart" which makes anaconda pick some defaults. If either of those variables are set, Beaker creates root and boot partitions with --fstype set unconditionally to ext3.
Comment 2 Dan Callaghan 2012-08-10 06:24:28 UTC 
We can introduce a ksmeta variable 'rootfstype' for this, with a default value of 'ext3'.
Comment 3 Dan Callaghan 2012-08-10 06:52:23 UTC 
On Gerrit: http://gerrit.beaker-project.org/1288
Comment 7 Dan Callaghan 2012-09-06 04:40:18 UTC 
Beaker 0.9.3 has been released.
Note You need to log in before you can comment on or make changes to this bug.