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.

Hi ,

I think i found the root reason , when i write something like

part / --fstype=ext4 --size=40960
part /tmp  --fstype=ext4 --size=20000
part swap --fstype=swap --size=1024
part pv.01 --size=10000

, then the profile will trigger the issue , but if use autopart , then everything will be okay.

Any susgestion suggestion?

(In reply to time.su from comment #3)
> Hi ,
> 
> I think i found the root reason , when i write something like
> 
> part / --fstype=ext4 --size=40960
> part /tmp  --fstype=ext4 --size=20000
> part swap --fstype=swap --size=1024
> part pv.01 --size=10000

Well, there's your problem. --fstype=ext4 is setting the fs type to ext4, overriding the default from the installclass. Use --fstype=xfs.

You can also omit the --fstype option completely to get the default fstype, which would in your case be xfs.