Bug 868999
Summary: | Attempting to update via yum -C produces database error Check uncompressed DB failed | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Josh Trutwin <jtrutwin> |
Component: | yum | Assignee: | Fedora Packaging Toolset Team <packaging-team> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | admiller, ffesti, james.antill, packaging-team, tim.lauridsen, zpavlas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-26 18:00:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Josh Trutwin
2012-10-22 17:37:08 UTC
Just a quick guess: cachedir has moved from /var/cache/yum/ to /var/cache/yum/$basearch/$releasever between F14 and F17.. I'd also suggest you look at "yum load-transaction", which is pretty much designed for your usecase. (In reply to comment #1) > Just a quick guess: cachedir has moved from /var/cache/yum/ to > /var/cache/yum/$basearch/$releasever between F14 and F17.. Actually both my fedora 14 and 17 systems have identical directory structures (other than 14 being 17) (In reply to comment #2) > I'd also suggest you look at "yum load-transaction", which is pretty much > designed for your usecase. Thanks for the pointer - the man page doesn't go into much detail, does this cause it to download on each system? The nice thing with copying the cache around is it avoided all the extra downloading. Is there any way to get this to work using the steps above? I unfortunately am also in the situation where I have NEARLY identical systems where a few might have one or two single additional RPMs installed, when reading up on load transation is says: "Note, however that the rpmdb version stored in the file must be identical to the version on the target system." which would make the load-transaction command fail. (In reply to comment #4) > (In reply to comment #2) > > I'd also suggest you look at "yum load-transaction", which is pretty much > > designed for your usecase. > > Thanks for the pointer - the man page doesn't go into much detail, does this > cause it to download on each system? Yes, load-transaction only does the actual transaction and not the rpms. So you still need to copy the cache of rpms about. I also noticed that you are copying the cache around with "scp -r" this is likely the root of the problem you are hitting. You need to preserve timestamps, so use "rsync -a -e ssh" (generally much easier/faster for things like this) or at worst "scp -rp". > The nice thing with copying the cache > around is it avoided all the extra downloading. Is there any way to get > this to work using the steps above? I unfortunately am also in the > situation where I have NEARLY identical systems where a few might have one > or two single additional RPMs installed, when reading up on load transation > is says: "Note, however that the rpmdb version stored in the file must be > identical to the version on the target system." which would make the > load-transaction command fail. Yes, I would recommend you not do this. Just install the extra rpms on all the computers so that "yum version" is the same on all of them, this will make your life a lot easier and less painful. Just a followup, the -p to scp/cp was the problem. Sorry for the noise. |