Page 1 of 1

Update to 5.0.22 from 5.0.20 through YUM fails

Posted: 17. Jun 2016, 21:03
by Tronmech
When I try to use yum and the repo file on the web site, I get this:

Code: Select all

[user@host Downloads]$ sudo yum update
Loaded plugins: ibm-check-lotus-updates, ibm-check-xorg-updates, ibm-repository,
              : langpacks, refresh-packagekit, versionlock
virtualbox                                               |  951 B     00:00     
virtualbox/7Workstation/x86_64 FAILED                                          
http://download.virtualbox.org/virtualbox/rpm/el/7Workstation/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
virtualbox/7Workstation/x86_64/primary                   | 4.4 kB     00:00     
http://download.virtualbox.org/virtualbox/rpm/el/7Workstation/x86_64/repodata/primary.xml.gz: [Errno -1] Metadata file does not match checksum
Trying other mirror.
Now, I'm about 1000% certain that this worked in 5.0.20, since YUM was about the ONLY way I was able to get it installed. (using a "mildly mutated by my company" RHEL 7.2).

Is this an actual upstream problem?

Re: Update to 5.0.22 from 5.0.20 through YUM fails

Posted: 17. Jun 2016, 21:12
by Martin
I've seen the same problem last year on RHEL 6.7 also on a company intranet.
It looked like something between my system and the download server was caching old repository metadata.
I was able to update by enabling one the company proxies in the yum configuraton which seemed to use another way through the net.

Re: Update to 5.0.22 from 5.0.20 through YUM fails

Posted: 17. Jun 2016, 21:50
by Tronmech
Lovely, given the way our company network is managed, much less how the INTERNET connection is managed, the odds of my getting this fixed are pretty slim.

Re: Update to 5.0.22 from 5.0.20 through YUM fails

Posted: 17. Jun 2016, 22:05
by Smackey's dad
Try clearing yum caches, if in fact this is a caching issue.

Re: Update to 5.0.22 from 5.0.20 through YUM fails

Posted: 18. Jun 2016, 09:54
by Martin
The problem was not yum caching in my case but a transparent caching proxy at the company Internet gateway.