Bug 1383407

Summary: Overcloud images from osp9 package have a root ext4 filesystem instead of xfs.
Product: Red Hat OpenStack Reporter: Sofer Athlan-Guyot <sathlang>
Component: rhosp-director-imagesAssignee: Thierry Vignaud <tvignaud>
Status: CLOSED ERRATA QA Contact: Omri Hochman <ohochman>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0 (Mitaka)CC: brad, dbecker, mburns, morazi, rhel-osp-director-maint, tvignaud
Target Milestone: asyncKeywords: ZStream
Target Release: 9.0 (Mitaka)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhosp-director-images-9.0-20161031.1.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-15 17:36:31 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:

Description Sofer Athlan-Guyot 2016-10-10 14:28:15 UTC
Description of problem:  installing overcloud images in OSP9 from rhosp-director-images-9.0-20160818.1.el7ost.noarch, give a ext4 root filesystem:


[root@overcloud-blockstorage-0 ~]# findmnt | grep '/ '
/ /dev/sda2   ext4 rw,relatime,seclabel,data=ordered


How reproducible: always


Steps to Reproduce:
1. install osp9 undercloud
2. upload image from rhosp-director-images-9.0-20160818.1.el7ost.noarch
3. spawn overcloud

Actual results: ext4 root filesystem


Expected results: xfs root filesystem

Comment 2 Brad P. Crochet 2016-10-13 16:24:18 UTC
FS_TYPE=xfs needs to be set in the environment when building images for OSPd9.

Comment 3 Thierry Vignaud 2016-10-13 16:41:25 UTC
upstream confirms the osp9 version of tripleo-common doesn't support for using 'environment' tag in the yaml.
We need to export FS_TYPE=xfs in http://pkgs.devel.redhat.com/cgit/rpms/rhosp-director-images/tree/overcloud-full.tdl?h=rhos-9.0-director-rhel-7#n16

OSP10 images eventually got fixed by https://github.com/openstack/tripleo-common/commit/a3182e7cd3042161fb7f58ae8c78dd308797dc2a

Comment 4 Thierry Vignaud 2016-10-17 18:19:28 UTC
The image build with that fix is using XFS:
$ virt-filesystems -a overcloud-full.qcow2 -l
Name      Type        VFS  Label       Size        Parent
/dev/sda  filesystem  xfs  img-rootfs  5067702272  -

Comment 7 Lon Hohberger 2016-11-07 21:29:03 UTC
[lhh@dhcp-10-19-61-117 tmp]$ guestfish

Welcome to guestfish, the guest filesystem shell for
editing virtual machine filesystems and disk images.

Type: 'help' for help on commands
      'man' to read the manual
      'quit' to quit the shell

><fs> add overcloud-full.qcow2
><fs> run
><fs> list-filesystems
/dev/sda: xfs

Tested with overcloud-full.tar from 20161031.1

Comment 8 Lon Hohberger 2016-11-07 21:29:39 UTC
[lhh@dhcp-10-19-61-117 tmp]$ virt-filesystems -a overcloud-full.qcow2 -l
Name      Type        VFS  Label       Size        Parent
/dev/sda  filesystem  xfs  img-rootfs  5246615552  -

Comment 10 errata-xmlrpc 2016-11-15 17:36:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2763.html