Images built using tripleo-common method have ext filesystem

[John Trowbridge]

When using the new tripleo-common script to build images[1] we get images with an ext filesystem because this is the default for DIB. However, we have been overriding this default in tripleoclient to get an xfs filesystem [2].

We need to update the tripleo-common yaml[3] to include this setting so that we don't regress that when changing to the new image building method.

[1] https://github.com/openstack/tripleo-common/blob/master/scripts/tripleo-build-images
[2] https://github.com/openstack/python-tripleoclient/blob/master/tripleoclient/v1/overcloud_image.py#L447
[3] https://github.com/openstack/tripleo-common/tree/master/image-yaml

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/369600

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/369600
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=a3182e7cd3042161fb7f58ae8c78dd308797dc2a
Submitter: Jenkins
Branch: master

commit a3182e7cd3042161fb7f58ae8c78dd308797dc2a
Author: Brad P. Crochet <email address hidden>
Date: Tue Sep 13 13:20:58 2016 -0400

    Add FS_TYPE xfs to RHEL and CentOS images

    The default fs type for DIB is ext, but some services need XFS,
    like Ceph. So, this sets the environment variable to enable
    an XFS fs.

    Change-Id: I5475040d6dee44fa952853ce513ca9f837d95be7
    Closes-Bug: #1622671

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-common 5.2.0 release.