Bug 1002261
| Summary: | btrfs partition specified in beaker job xml results in bad kickstart file: Unknown command: btrfs | ||
|---|---|---|---|
| Product: | [Retired] Beaker | Reporter: | Guangze Bai <gbai> |
| Component: | general | Assignee: | Nick Coghlan <ncoghlan> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Amit Saha <asaha> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 0.14 | CC: | aigao, asaha, dcallagh, ebaak, eguan, llim, qcai, qwan, qzhao, rmancy, xjia, yshao |
| Target Milestone: | 0.14.2 | Keywords: | Regression, Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-11-07 01:47:13 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Guangze Bai
2013-08-28 18:33:56 UTC
Support for 'btrfs' command was only added in anaconda-17.3 It seems RHEL6 must use an older version of anaconda. 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. On Gerrit: http://gerrit.beaker-project.org/2207 Beaker 0.15 has been released. 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. 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. Closing as addressed in Beaker 0.14.2. |