Bug 1002261 - btrfs partition specified in beaker job xml results in bad kickstart file: Unknown command: btrfs
Summary: btrfs partition specified in beaker job xml results in bad kickstart file: Un...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Beaker
Classification: Retired
Component: general
Version: 0.14
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 0.14.2
Assignee: Nick Coghlan
QA Contact: Amit Saha
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-28 18:33 UTC by Guangze Bai
Modified: 2018-02-06 00:41 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-07 01:47:13 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 973595 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 973595

Description Guangze Bai 2013-08-28 18:33:56 UTC
Description of problem:

https://beaker.engineering.redhat.com/recipes/1011313
http://beaker-archive.app.eng.bos.redhat.com/beaker-logs/2013/08/4794/479472/1011313/console.log
https://beaker.engineering.redhat.com/kickstart/428909

This is a RHEL6 install, and I put a series of different filesystem partitions in job xml:
===
<partitions>
	<partition fs="ext3" name="/ext3" size="3" type="part"/>
	<partition fs="ext2" name="/ext2" size="3" type="part"/>
	<partition fs="xfs" name="/xfs" size="3" type="part"/>
	<partition fs="btrfs" name="/btrfs" size="3" type="part"/>
</partitions>
===

But anaconda complains as the console.log showed:
===
+ python /tmp/anamon --recipe-id 1011313 --xmlrpc-url http://lab-02.rhts.eng.rdu.redhat.com:8000/RPC2 
TrueThe following error was found while parsing the kickstart configuration file: 
 
The following problem occurred on line 56 of the kickstart file: 
 
Unknown command: btrfs 
 
install exited abnormally [1/1]  
The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. 
===

And where kickstart contains:
===
part /boot --size 200 --recommended --asprimary
part / --size 1024 --grow
part swap --recommended
part /ext3 --size=3072 --fstype ext3
part /ext2 --size=3072 --fstype ext2
part /xfs --size=3072 --fstype xfs
part btrfs.btrfs --size=3072
btrfs /btrfs --label=btrfs btrfs.btrfs    (line 56)
===

Version-Release number of selected component (if applicable):

How reproducible:
always

Actual results:
Install Failed.

Expected results:
Install can succeed.

Additional info:

Comment 2 Raymond Mancy 2013-08-29 00:44:13 UTC
Support for 'btrfs' command was only added in anaconda-17.3
It seems RHEL6 must use an older version of anaconda.

Comment 3 Nick Coghlan 2013-08-29 04:23:32 UTC
Unfortunately, when bug 973595 was addressed to support btrfs partitions on RHEL 7, we didn't account for the fact that anaconda previously supported creating btrfs volumes using the same syntax as other filesystems, so the kickstart partitioning changes to support RHEL 7 broke the btrfs technical preview in RHEL 6.

The new commands need to be guarded with a template check like "if distro is not osmajor('RedHatEnterpriseLinux6')". Once such an improved snippet was available and tested, it could be added to "/etc/beaker/snippets/rhts_partitions" as a workaround for existing installations prior to upgrading Beaker.

Comment 4 Nick Coghlan 2013-09-04 05:07:11 UTC
On Gerrit: http://gerrit.beaker-project.org/2207

Comment 7 Nick Coghlan 2013-10-03 02:29:02 UTC
Beaker 0.15 has been released.

Comment 8 Raymond Mancy 2013-10-23 01:57:18 UTC
This change has been nominated to be back ported to the 0.14 branch, to be released as part of the next maintenance release 0.14.2.

Comment 9 Nick Coghlan 2013-10-25 06:36:14 UTC
Adjusting target milestone to make the changes backported to 0.14.2 easier to identify. 0.15.0 has enough significant regressions that it shouldn't be used, so the change means that 0.15.1 can be effectively reidentified as the union of that tag and the 0.14.2 target milestone.

Comment 12 Nick Coghlan 2013-11-07 01:47:13 UTC
Closing as addressed in Beaker 0.14.2.


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