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.

Resolved by upstream commit: https://github.com/upgrades-migrations/preupgrade-assistant/commit/a01f099a2b4237e267d902c5e7e3d437e8710ca3

I cannot reproduce this.

This was originally found in 2.2.1-1.el5.  On el6 channel, the last version is 2.1.10-6.el6, so my guess is that the problematic code was never released.

Michal, can you please confirm if that is the case?  If so, I would propose dropping this from erratum and closing it (there is nothing to fix from RHEL6 customer POV).  Otherwise, please provide hint how to reproduce this on RHEL6.

Alois, to reproduce this in 2.1.10-6.el6, make sure you have "autopart" in /root/anaconda-ks.cfg - it serves as a basis for the generated kickstart.

When generating kickstart the "part" commands were always added no matter whether there was "autopart" already or not.

Sorry, this does not work: 2.1.10 still passes, no errors seen.

(It did work for bug 1414341, where I have asked very similar question; sorry if I made it confusing.)

Ok, it's possible that this bug, describing different results when executing the same command twice, is related to a development version of the Preupgrade Assistant. I have no other ideas on how to reproduce it. I'll close and drop it from the Erratum.