Note: This is a false positive. We got this in the log: 14:40:46 [upgrade-from-prevrelease-suit] + sudo yum -y install python34-PyYAML PyYAML 14:40:46 [upgrade-from-prevrelease-suit] Loaded plugins: fastestmirror 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] One of the configured repositories failed (Unknown), 14:40:46 [upgrade-from-prevrelease-suit] and yum doesn't have enough cached data to continue. At this point the only 14:40:46 [upgrade-from-prevrelease-suit] safe thing yum can do is fail. There are a few ways to work "fix" this: 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 1. Contact the upstream for the repository and get them to fix the problem. 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 2. Reconfigure the baseurl/etc. for the repository, to point to a working 14:40:46 [upgrade-from-prevrelease-suit] upstream. This is most often useful if you are using a newer 14:40:46 [upgrade-from-prevrelease-suit] distribution release than is supported by the repository (and the 14:40:46 [upgrade-from-prevrelease-suit] packages for the previous distribution release still work). 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 3. Run the command with the repository temporarily disabled 14:40:46 [upgrade-from-prevrelease-suit] yum --disablerepo=<repoid> ... 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 4. Disable the repository permanently, so yum won't use it by default. Yum 14:40:46 [upgrade-from-prevrelease-suit] will then just ignore the repository until you permanently enable it 14:40:46 [upgrade-from-prevrelease-suit] again or use --enablerepo for temporary usage: 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] yum-config-manager --disable <repoid> 14:40:46 [upgrade-from-prevrelease-suit] or 14:40:46 [upgrade-from-prevrelease-suit] subscription-manager repos --disable=<repoid> 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] 5. Configure the failing repository to be skipped, if it is unavailable. 14:40:46 [upgrade-from-prevrelease-suit] Note that yum will try to contact the repo. when it runs most commands, 14:40:46 [upgrade-from-prevrelease-suit] so will have to try and fail each time (and thus. yum will be be much 14:40:46 [upgrade-from-prevrelease-suit] slower). If it is a very temporary problem though, this is often a nice 14:40:46 [upgrade-from-prevrelease-suit] compromise: 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true 14:40:46 [upgrade-from-prevrelease-suit] 14:40:46 [upgrade-from-prevrelease-suit] Cannot find a valid baseurl for repo: centos-base-el7 So the issue is with the CentOS repos on the slaves. This should be fixed by: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 On 25 July 2017 at 18:10, oVirt Jenkins <jenkins@ovirt.org> wrote:

Change 79700,5 (vdsm) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed.

This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed.

For further details about the change see: https://gerrit.ovirt.org/#/c/79700/5

For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/1500/ _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra

-- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted