[ https://ovirt-jira.atlassian.net/browse/OVIRT-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22601#comment-22601 ] eyal edri [Administrator] commented on OVIRT-828: ------------------------------------------------- bin', 'SHELL': '/bin/bash', 'PS1': '<mock-chroot> \\s-\\v\\$ ', 'LD_PRELOAD': '/tmp/tmpuh9e19lk/$LIB/nosync.so', 'PROMPT_COMMAND': 'printf "\\033]0;<mock-chroot>\\007"', 'TERM': 'vt100', 'LC_MESSAGES': 'C', 'HOME': '/builddir', 'LANG': 'en_US.UTF-8'} and shell False DEBUG util.py:421: Yum command has been deprecated, use dnf instead. DEBUG util.py:421: See 'man dnf' and 'man yum2dnf' for more information. DEBUG util.py:421: http://resources.ovirt.org/pub/ovirt-4.0-snapshot-static/rpm/fc24/repodata/r...: [Errno 14] HTTP Error 404 - Not Found DEBUG util.py:421: Trying other mirror. DEBUG util.py:421: One of the configured repositories failed ("Custom ovirt-snapshot-static"), DEBUG util.py:421: and yum doesn't have enough cached data to continue. At this point the only DEBUG util.py:421: safe thing yum can do is fail. There are a few ways to work "fix" this: DEBUG util.py:421: 1. Contact the upstream for the repository and get them to fix the problem. DEBUG util.py:421: 2. Reconfigure the baseurl/etc. for the repository, to point to a working DEBUG util.py:421: upstream. This is most often useful if you are using a newer DEBUG util.py:421: distribution release than is supported by the repository (and the DEBUG util.py:421: packages for the previous distribution release still work). DEBUG util.py:421: 3. Disable the repository, so yum won't use it by default. Yum will then DEBUG util.py:421: just ignore the repository until you permanently enable it again or use DEBUG util.py:421: --enablerepo for temporary usage: DEBUG util.py:421: yum-config-manager --disable ovirt-snapshot-static DEBUG util.py:421: 4. Configure the failing repository to be skipped, if it is unavailable. DEBUG util.py:421: Note that yum will try to contact the repo. when it runs most commands, DEBUG util.py:421: so will have to try and fail each time (and thus. yum will be be much DEBUG util.py:421: slower). If it is a very temporary problem though, this is often a nice DEBUG util.py:421: compromise: DEBUG util.py:421: yum-config-manager --save --setopt=ovirt-snapshot-static.skip_if_unavailable=true DEBUG util.py:421: failure: repodata/repomd.xml from ovirt We've had some DDOS attacks recently on our repository and we're looking into ways to handle with it, but it might take some time, Unfortunately for now the best option is just to retrigger the patch, I see http://resources.ovirt.org/pub/ is up and accessible now.
ovirt-engine_master_check-patch-fc24-x86_64 failing ---------------------------------------------------
Key: OVIRT-828 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-828 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Greg Sheremeta Assignee: infra
http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-fc24-x86_64/689... Doesn't appear related to the patch.
17:52:04 Finish: cleaning yum metadata 17:52:04 Mock Version: 1.2.21 17:52:04 INFO: Mock Version: 1.2.21 17:52:04 Start: yum install 17:52:09 ERROR: Command failed. See logs for output. 17:52:09 # /usr/bin/yum-deprecated --installroot /var/lib/mock/fedora-24-x86_64-a84bda050a5e85bcae66e67894bf5f93-17376/root/ --releasever 24 install @buildsys-build --setopt=tsflags=nocontexts 17:52:09 Init took 6 seconds
Thanks, Greg -- Greg Sheremeta, MBA Red Hat, Inc. Sr. Software Engineer gshereme@redhat.com
-- This message was sent by Atlassian JIRA (v1000.526.2#100018)