Created attachment 1111931 [details] Screenshot of error Description of problem: Trying to deploy a new system from Satellite using synched RHEL 7.2 kickstart image fails. VM is created (RHEV) boots and starts anaconda then fails creating volumes with the following error: "Value Error: new value nonexistent xfs filesystem is not valid as default fs type" self._check_valid_fstype(newtype) File "/usr/lib/python2.7/site-packages/blivet/__init__.py" Same profiles and partition table work fine with 7.1 Version-Release number of selected component (if applicable): Satellite 6.1.5 RHEL Kickstart 7.2 How reproducible: Always Steps to Reproduce: 1. create a partition table in Satellite e.g. zerombr clearpart --all --initlabel autopart 2. create a new host and select 7.2 kickstart media 3. submit the creation Actual results: "Value Error: new value nonexistent xfs filesystem is not valid as default fs type" self._check_valid_fstype(newtype) File "/usr/lib/python2.7/site-packages/blivet/__init__.py" Expected results: installation proceeds normally Additional info: Attached screenshot Attached treeinfo from kickstart
Created attachment 1111932 [details] treeinfo from kickstart dir
Moving 6.2 bugs out to sat-backlog.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.