This is a multi-part message in MIME format. --------------E92BB960D76982341190E690 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 / --------------E92BB960D76982341190E690 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=utf-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> <p>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.</p> <p>The installer says<i> </i>it cannot queue package iproute. <br> </p> <p>Is there a repo down or that has changed? Thanks for any suggestions.<br> </p> <p>It appears yum is also broken:<i><br> </i></p> <p><i>yum update<br> Loaded plugins: fastestmirror, imgbased-persist, package_upload, product-id,<br> : search-disabled-repos, subscription-manager<br> This system is not registered with an entitlement server. You can use subscription-manager to register.<br> centos-opstools-release | 2.9 kB 00:00 <br> ovirt-4.1 | 3.0 kB 00:00 <br> ovirt-4.1-centos-gluster38 | 2.9 kB 00:00 <br> <br> <br> One of the configured repositories failed (Unknown),<br> and yum doesn't have enough cached data to continue. At this point the only<br> safe thing yum can do is fail. There are a few ways to work "fix" this:<br> <br> 1. Contact the upstream for the repository and get them to fix the problem.<br> <br> 2. Reconfigure the baseurl/etc. for the repository, to point to a working<br> upstream. This is most often useful if you are using a newer<br> distribution release than is supported by the repository (and the<br> packages for the previous distribution release still work).<br> <br> 3. Run the command with the repository temporarily disabled<br> yum --disablerepo=<repoid> ...<br> <br> 4. Disable the repository permanently, so yum won't use it by default. Yum<br> will then just ignore the repository until you permanently enable it<br> again or use --enablerepo for temporary usage:<br> <br> yum-config-manager --disable <repoid><br> or<br> subscription-manager repos --disable=<repoid><br> <br> 5. Configure the failing repository to be skipped, if it is unavailable.<br> Note that yum will try to contact the repo. when it runs most commands,<br> so will have to try and fail each time (and thus. yum will be be much<br> slower). If it is a very temporary problem though, this is often a nice<br> compromise:<br> <br> yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true<br> <br> Cannot retrieve metalink for repository: ovirt-4.1-epel/x86_64. Please verify its path and try again<br> </i><br> </p> </body> </html> --------------E92BB960D76982341190E690--