[ovirt-users] Node Next Install Problem

[Matt Simonsen]

I installed based on an older Node Next DVD (4.1.7) that has worked in 
the past and it doesn't appear to be working when I add it to a cluster.

The installer says//it cannot queue package iproute.

Is there a repo down or that has changed? Thanks for any suggestions.

It appears yum is also broken:/
/

/yum update
Loaded plugins: fastestmirror, imgbased-persist, package_upload, product-id,
               : search-disabled-repos, subscription-manager
This system is not registered with an entitlement server. You can use 
subscription-manager to register.
centos-opstools-release                                 | 2.9 kB     00:00
ovirt-4.1                                               | 3.0 kB     00:00
ovirt-4.1-centos-gluster38                              | 2.9 kB     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=<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: ovirt-4.1-epel/x86_64. Please 
verify its path and try again
/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20180308/426aec33/attachment.html>