On 05/15/2018 01:26 AM, Sahina Bose wrote:
On Tue, May 15, 2018 at 5:02 AM, John Florian <jflorian@doubledog.org <mailto:jflorian@doubledog.org>> wrote:
When I run engine-setup, I get this error:
[ ERROR ] Yum [u'Errors were encountered while downloading packages.', u'gdeploy-2.0.6-1.el7.noarch: failure: gdeploy-2.0.6-1.el7.noarch.rpm from ovirt-4.1-centos-gluster38: [Errno 256] No more mirrors to try.\nhttp://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/gdeploy-2.0.6-1... <http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/gdeploy-2.0.6-1.el7.noarch.rpm>: [Errno 14] HTTP Error 404 - Not Found'] [ ERROR ] Failed to execute stage 'Package installation': [u'Errors were encountered while downloading packages.', u'gdeploy-2.0.6-1.el7.noarch: failure: gdeploy-2.0.6-1.el7.noarch.rpm from ovirt-4.1-centos-gluster38: [Errno 256] No more mirrors to try.\nhttp://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/gdeploy-2.0.6-1... <http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/gdeploy-2.0.6-1.el7.noarch.rpm>: [Errno 14] HTTP Error 404 - Not Found']
If I go exploring with my browser, it doesn't appear that http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8 <http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8> exists any more. The oldest there is 3.10. I didn't see any mention of needing to revise this repo config, but I obviously must have missed something.
This is discussed in thread https://www.mail-archive.com/users@ovirt.org/msg48116.html
You can edit the repo file to add the latest 3.12 gluster repo
Seeing that the 3.12 repo was enabled as part of ovirt-release42-4.2.3-1.el7.centos.noarch I just disabled the unreachable repo for 3.8. That got my engine upgraded to 4.2.3. Now I'm trying to tackle my two hosts. I put the first into maintenance and then tried the upgrade through the web UI but this failed. I tried running a yum update from a shell on that host and found a similar problem, now with ovirt-4.1 repo. So I disabled that, retried the yum update and got/applied lots of updates to bring the host up to CentOS 7.5. I then retried the upgrade through the web UI and this is still failing and I'm having trouble figuring out why. What logs do I need to be looking at for host upgrades? -- John Florian