Red Hat Bugzilla – Bug 590340
Move rpmdb cache to persistent storage
Last modified: 2014-01-21 01:17:33 EST
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.