Upgrade 3.0.1.4 -> 3.0.1.8 failed

Report bugs and workarounds
Post Reply
urmet
Posts: 3
Joined: 28 Feb 2017 20:44

Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by urmet »

Hello.

Upgrading from 3.0.14 got this message:
Image

What is solution?

Br,
Urmet
User avatar
shawniverson
Posts: 3649
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by shawniverson »

urmet
Posts: 3
Joined: 28 Feb 2017 20:44

Re: Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by urmet »

Hello.

I've tried to do second step:
yum check-update ca-certificates; (($?==100)) && yum update ca-certificates || yum reinstall ca-certificates

But then this error:
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist https://dl.efa-project.org/rpm/mirrors-efa error was
14: PYCURL ERROR 77 - "Problem with the SSL CA cert (path? access rights?)"
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
Loaded plugins: fastestmirror, security
Setting up Reinstall Process
Loading mirror speeds from cached hostfile
Could not retrieve mirrorlist https://dl.efa-project.org/rpm/mirrors-efa error was
14: PYCURL ERROR 77 - "Problem with the SSL CA cert (path? access rights?)"
Error: Cannot retrieve metalink for repository: epel. Please verify its path and try again
User avatar
shawniverson
Posts: 3649
Joined: 13 Jan 2014 23:30
Location: Indianapolis, Indiana USA
Contact:

Re: Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by shawniverson »

You may need to disable some repositories temporarily as you work on your ca-certificate issue.

Take a look in /etc/yum.repos.d and disable the affected repos temporarily by setting enabled=0 for them.

When your issue is fixed, be sure to set them back to enabled=1.
urmet
Posts: 3
Joined: 28 Feb 2017 20:44

Re: Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by urmet »

Thank you.

Disabling repositories temporarily worked.
Now I can upgrade EFA.
stuarthurst
Posts: 16
Joined: 10 Jan 2017 17:36

Re: Upgrade 3.0.1.4 -> 3.0.1.8 failed

Post by stuarthurst »

Thanks +1

This fixed mine too as it hadn't been able to upgrade since 3.0.1.7
Just upgrading it now to 3.0.1.9 and on-wards.
Post Reply