Bug 915272

Anaconda changed the meaning, now it's one of: "lvm, btrfs, plain", and I can't see an option to choose default filesystem type without using 'part' or 'logvol'.

Potentially related, note that bug 908354 allows Beaker 0.13.2+ to create simple btrfs partitions with recent anaconda versions.

(In reply to Nick Coghlan from comment #3)
> Potentially related, note that bug 908354 allows Beaker 0.13.2+ to create
> simple btrfs partitions with recent anaconda versions.

The BZ number above doesn't look correct.

To clarify: this BZ is about having some simple way to choose root file system (xfs/ext4/btrfs) without the need for custom kickstarts.

Sorry, I meant bug 973595 for the current btrfs support in Beaker 0.13/14/15. I don't how I came up with the previous incorrect bug reference.

Currently we have this line at the end of Server/bkr/server/snippets/rhts_partitions:


#}
autopart
{% endif %}

So, to implement this feature we could have something like this instead (in semi pseudo-code):

{% if autopart_type and distro is "Fedora18+" or distro is "RHEL7+" %}
autopart --type autopart_type
{% else %}
autopart
{%endif%}

PS: FWIW, this seems to have been added to anaconda in this commit: https://git.fedorahosted.org/cgit/anaconda.git/commit/?id=eb17cee2b0a9185795509fa7c32405a974b9589e

Yes, that looks good to me. That way, setting rootfstype will still mean avoiding autopart entirely, while setting the new autopart_type option will allow autopart to be configured appropriately.

Great, the patch is up on Gerrit: http://gerrit.beaker-project.org/#/c/2688/1

(In reply to Jan Stancek from comment #5)
> (In reply to Nick Coghlan from comment #3)
> > Potentially related, note that bug 908354 allows Beaker 0.13.2+ to create
> > simple btrfs partitions with recent anaconda versions.
> 
> The BZ number above doesn't look correct.
> 
> To clarify: this BZ is about having some simple way to choose root file
> system (xfs/ext4/btrfs) without the need for custom kickstarts.

The wiki page [1] mentions that the value for "--type" should be a partitioning scheme,  not a file system type. In fact, Anaconda merrily accepted "xfs" as a type and used "xfs" to create the partitions. So, either the wiki page needs updating or this is a bug in Anaconda. 

Or, am I confused?

[1] http://fedoraproject.org/wiki/Anaconda/Kickstart#autopart

For "lvm", it's going to create LVM. Indeed it works.
[root@dev-kvm-guest-01 ~]# df -TH
Filesystem                                Type      Size  Used Avail Use% Mounted on
/dev/mapper/rhel_dev--kvm--guest--01-root xfs        19G  1.7G   18G   9% /
devtmpfs                                  devtmpfs  516M     0  516M   0% /dev
tmpfs                                     tmpfs     522M     0  522M   0% /dev/shm
tmpfs                                     tmpfs     522M  6.9M  515M   2% /run
tmpfs                                     tmpfs     522M     0  522M   0% /sys/fs/cgroup
/dev/sda1                                 xfs       507M  105M  403M  21% /boot

For beaker, have added autopart_type to allow user's to specify --type, what Anaconda does with it is a different point. So verify this bug.

This change is included in the Beaker 0.15.3 maintenance release:

http://beaker-project.org/docs/whats-new/release-0.15.html#beaker-0-15-3