Loaded plugins: fastestmirror, langpacks
Loading mirror speeds from cached hostfile
One of the configured repositories failed (Unknown),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=<repoid> ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable <repoid>
or
subscription-manager repos --disable=<repoid>
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
OpenNebula Community Edition 0.0 B/s | 0 B 00:00
Errors during downloading metadata for repository ‘opennebula’:
Curl error (60): Peer certificate cannot be authenticated with given CA certificates for https://downloads.opennebula.io/repo/5.12/CentOS/8/x86_64/repodata/repomd.xml [SSL certificate problem: certificate is not yet valid]
Error: Failed to download metadata for repo ‘opennebula’: Cannot download repomd.xml: Cannot download repodata/repomd.xml: All mirrors were tried
One of the configured repositories failed (OpenNebula Enterprise Edition),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=opennebula ...
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable opennebula
or
subscription-manager repos --disable=opennebula
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=opennebula.skip_if_unavailable=true
failure: repodata/repomd.xml from opennebula: [Errno 256] No more mirrors to try. https://<token>@enterprise.opennebula.io/repo/5.12/CentOS/7/x86_64/repodata/repomd.xml: [Errno 14] HTTPS Error 401 - Unauthorized
[root@localhost ~]# cd /etc/yum.repos.d
[root@localhost yum.repos.d]# ls
CentOS-Base.repo CentOS-Debuginfo.repo CentOS-Sources.repo CentOS-fasttrack.repo opennebula.repo
CentOS-CR.repo CentOS-Media.repo CentOS-Vault.repo CentOS-x86_64-kernel.repo
[root@localhost yum.repos.d]# rm opennebula.repo
rm: remove regular file ‘opennebula.repo’? y
[root@localhost yum.repos.d]# cat << “EOT” > /etc/yum.repos.d/opennebula.repo