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.

Description of problem:
 Atm. the rpmdb cache is in /var/cache/yum/... we've recently moved this (upstream) to /var/lib/yum/rpmdb-indexes because mock will copy all of /var/cache/yum, and then we have problems when the cache doesn't match the rpmdb. We have a workaround for this by using ctime in RHEL-6, but upstream still uses mtime (so we are needlessly different).

 It's also possible that people will share all of /var/cache/yum over NFS/rsync, and thus. run into the same problems.

 Fix is simple, we just change the path.

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

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

I believe this is also impacting the building of LiveCDs in Koji. The yum cache directory left over from the creation of the LiveCD image contains an "installed" directory which makes the Koji code choke. 

This comment is just to make other Rel-Eng folks aware of the issue, I'm going to fix the fragile Koji code myself.

There's a patch for mock in upstream which fixes the mock issue.

is the livecd creator using mock at all?

Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.