Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1110789 [details]
Screen shot of installer error

Description of problem:
Provisioning from Satellite 6.1.5 to RHEV 3.4 specifying 7.2 kickstart media 
(treeinfo attached)

using any partition table


install fails when creating volumes 
"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"

Version-Release number of selected component (if applicable):


How reproducible:
always - even deleted all my Satellite content and re-installed
Deployment works fine with 7.1 kickstart image

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 1110802 [details]
treeinfo file from kickstart tree

FWIW the image you attached is not an installer error message.

Something in the media is missing that is needed to support XFS. That probably means either that your kernel does not match the media (it must) or you have custom media that has issues (eg: missing xfs utilities).

Thanks David, didn't know where to put this one... Kickstart image, so figured it might land here. Rebuilt my Satellite Server and content. Still happens. Who do we ping on this one?

This error usually indicates that you have a mismatch between the kernel you are using and the initrd and/or stage2 image. You have to make sure that they are all from the same installer media. You can't mix, say, a RHEL 7.1 kernel with the initrd/stage2 from rhel7.2

OK. Well. I guess I need to move this over to the Satellite team or the CDN team as the content is not coming down to the Satellite properly. I am not building the kickstart images nor configuring their component locations. I am simply synching up the content to my Satellite and deploying systems. It results in the aforementioned error.

marking closed not a bug