Re: [ovirt-users] oVirt repo errors..

[Alexander Witte]

Disregard, figured it out- system clock was wrong.  Sorry!

Alex Witte


On Sep 21, 2017, at 2:20 PM, Alexander Witte 
mailto:alexander.wi...@baicanada.com>> wrote:

I seem to get this error with multiple oVirt repos (4.0, 4.1).  I’m just trying 
to install the hosted engine on a fresh Centos 7.4 server...

Can someone please point me in the direction of what I am doing wrong?


[root@localhost ~]# yum install ovirt-hosted-engine-setup
Loaded plugins: fastestmirror
base

 | 3.6 kB  00:00:00
centos-opstools-release 

 | 2.9 kB  00:00:00
extras  

 | 3.4 kB  00:00:00
ovirt-4.1   

 | 3.0 kB  00:00:00
ovirt-4.1-centos-gluster38  

 | 2.9 kB  00:00:00


 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= ...

 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 
or
subscription-manager repos --disable=

 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=.skip_if_unavailable=true

Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify 
its path and try again
[root@localhost ~]#

[root@localhost ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
[root@localhost ~]#

Sorry if I’m dumb.

Alex

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] oVirt repo errors..

[Alexander Witte]

I seem to get this error with multiple oVirt repos (4.0, 4.1).  I’m just trying 
to install the hosted engine on a fresh Centos 7.4 server...

Can someone please point me in the direction of what I am doing wrong?


[root@localhost ~]# yum install ovirt-hosted-engine-setup
Loaded plugins: fastestmirror
base

 | 3.6 kB  00:00:00
centos-opstools-release 

 | 2.9 kB  00:00:00
extras  

 | 3.4 kB  00:00:00
ovirt-4.1   

 | 3.0 kB  00:00:00
ovirt-4.1-centos-gluster38  

 | 2.9 kB  00:00:00


 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= ...

 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 
or
subscription-manager repos --disable=

 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=.skip_if_unavailable=true

Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify 
its path and try again
[root@localhost ~]#

[root@localhost ~]# cat /etc/centos-release
CentOS Linux release 7.4.1708 (Core)
[root@localhost ~]#

Sorry if I’m dumb.

Alex

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users