- Infra - oVirt List Archives

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 08 Dec '17

08 Dec '17

This is a multi-part message in MIME format... ------------=_1512763653-17340-252 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- {quote} Perhaps just use old versions of the container? Example: https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.4.0-einsteinium uses Firefox 54 {quote} Yep. This is what Docker tags are for... In fact, we should probably set things up so that we always use specific tagged versions in tests rather then '{{:latest}}', so that we don't introduce a rouge source of change to our testing apparatus. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512763653-17340-252 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>{quote} Perhaps just use old versions of the container? Example: <a href="https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.4.0-einsteinium">https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.4.0-einsteinium</a> uses Firefox 54 {quote}</p> <p>Yep. This is what Docker tags are for…</p> <p>In fact, we should probably set things up so that we always use specific tagged versions in tests rather then ‘{{:latest}}’, so that we don't introduce a rouge source of change to our testing apparatus.</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512763653-17340-252--

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 08 Dec '17

08 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- One issue I see is that the provided containers use only the latest browser. Example: https://github.com/SeleniumHQ/docker-selenium/blob/master/NodeFirefox/Docke… ARG FIREFOX_VERSION=57.0.1 Any ideas on how we could use older browsers too? Perhaps just use old versions of the container? Example: https://github.com/SeleniumHQ/docker-selenium/releases/tag/3.4.0-einsteinium uses Firefox 54 > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #986
by jenkins＠jenkins.phx.ovirt.org 08 Dec '17

08 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/986/displa…> Changes: [Anton Marchukov] Enabled repoman builds on Fedora 27. ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 9c4d074e30ec2f38daa27431716bc75d33eb8fbe (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 9c4d074e30ec2f38daa27431716bc75d33eb8fbe Commit message: "Enabled repoman builds on Fedora 27." > git rev-list b8d7eb1564528a26affca81548a5f84249e690aa # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins357930039576039284.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1474, in _commonLoadRepoXML if self._latestRepoXML(local): File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1443, in _latestRepoXML oxml = self._saveOldRepoXML(local) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1300, in _saveOldRepoXML shutil.copy2(local, old_local) File "/usr/lib64/python2.7/shutil.py", line 131, in copy2 copystat(src, dst) File "/usr/lib64/python2.7/shutil.py", line 98, in copystat os.utime(dst, (st.st_atime, st.st_mtime)) OSError: [Errno 2] No such file or directory: '/home/jenkins/mirrors_cache/centos-extras-el7/repomd.xml.old.tmp' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 84787,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 07 Dec '17

07 Dec '17

Change 84787,3 (ovirt-engine) 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/84787/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4331/

1 0

oVirt infra weekly meeting notes 06.12.2017
by Evgheni Dereveanchin 07 Dec '17

07 Dec '17

Hi everyone, Please find the topics of this week's infra meeting below: PHX DC: - Overview of infra and documentation <http://ovirt-infra-docs.readthedocs.io/> - PHX upgrade to 4.2 progressing <https://ovirt-jira.atlassian.net/browse/OVIRT-1735>, some more bugs identified - Status.ovirt.org moved to OpenShift AI: - Add a link to Jira on this <http://ovirt-infra-docs.readthedocs.io/en/latest/General/Communication/inde…> page - patch <https://gerrit.ovirt.org/#/c/85190/> - Find some entry level tickets to assign to volunteers - Backup persistent data on OpenShift? - Move all web hosting to Openshift? Candidates: - www.ovirt.org - stats.ovirt.org - templates.ovirt.org -- Regards, Evgheni Dereveanchin

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 07 Dec '17

07 Dec '17

This is a multi-part message in MIME format... ------------=_1512641905-10461-119 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- [~gshereme(a)redhat.com] I don't know enough about how to use Selenium to iterate on this on my own, so I'll try to guide you through what I think is needed to be done. If you want more hand-on help from me, you'll need to teach me a little about Selenium and perhaps give me a small example app I can iterate with... Here are the things that need to be done # Enable the OST suit to use docker - this is done by: ## Adding '{{docker}}' to the '{{*.packages}}' file of the suit ## Adding '{{docker}}' to the '{{*.packages}}' file of '{{check-patch}}' (So code changes to the suit can be tested). ## Add the following to the relevant '{{*.mounts}}' files {code}/var/run/docker.sock:/var/run/docker.sock{code} # Start up the Selenium containers from inside the suit and make them able to talk to oVirt. The readme of the GitHub repo gives examples of '{{docker}}' commands doing that, but those use the deprecated '{{--link}}' option. I've looked at what the containers actually do, and is seems that the browser containers simply expect the '{{HUB_PORT_4444_TCP_ADDR}}' and '{{HUB_PORT_4444_TCP_PORT}}' environment variables to be defined for them and pointing to the hub container. A more modern approach to setting this up would be: ## Setup a Docker network to connect the containers together ## Setup the hostnames for the oVirt VMs in the Docker network ## Start up a hub container and expose port 4444 so test suits can connect to it. ## Start up the browser containers and configure the env vars for then so they can find the hub container The above could be done with a bunch of Docker commands, but a better approach would be to use an automation tool such as '{{docker-compose}}'. But given that Ansible is closer to home for us, and likely to be used by other oVirt components, I think '{{ansible-containers}}' would be a better choice here. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512641905-10461-119 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] I don't know enough about how to use Selenium to iterate on this on my own, so I'll try to guide you through what I think is needed to be done. If you want more hand-on help from me, you'll need to teach me a little about Selenium and perhaps give me a small example app I can iterate with…</p> <p>Here are the things that need to be done # Enable the OST suit to use docker – this is done by: ## Adding ‘{{docker}}’ to the ‘{{*.packages}}’ file of the suit ## Adding ‘{{docker}}’ to the ‘{{*.packages}}’ file of ‘{{check-patch}}’ (So code changes to the suit can be tested). ## Add the following to the relevant ‘{{*.mounts}}’ files</p> <pre>{code}/var/run/docker.sock:/var/run/docker.sock{code}</pre> <p># Start up the Selenium containers from inside the suit and make them able to talk to oVirt. The readme of the GitHub repo gives examples of ‘{{docker}}’ commands doing that, but those use the deprecated ‘{{--link}}’ option. I've looked at what the containers actually do, and is seems that the browser containers simply expect the ‘{{HUB_PORT_4444_TCP_ADDR}}’ and ‘{{HUB_PORT_4444_TCP_PORT}}’ environment variables to be defined for them and pointing to the hub container. A more modern approach to setting this up would be: ## Setup a Docker network to connect the containers together ## Setup the hostnames for the oVirt VMs in the Docker network ## Start up a hub container and expose port 4444 so test suits can connect to it. ## Start up the browser containers and configure the env vars for then so they can find the hub container</p> <pre>The above could be done with a bunch of Docker commands, but a better approach would be to use an automation tool such as '{{docker-compose}}'. But given that Ansible is closer to home for us, and likely to be used by other oVirt components, I think '{{ansible-containers}}' would be a better choice here.</pre> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512641905-10461-119--

1 0

Build failed in Jenkins: system-sync_mirrors-epel-el6-x86_64 #984
by jenkins＠jenkins.phx.ovirt.org 07 Dec '17

07 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/984/displa…> Changes: [Yedidyah Bar David] wgt: Fix excludes ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-epel-el6-x86_64/ws/> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision b8d7eb1564528a26affca81548a5f84249e690aa (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f b8d7eb1564528a26affca81548a5f84249e690aa Commit message: "wgt: Fix excludes" > git rev-list bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 # timeout=10 [system-sync_mirrors-epel-el6-x86_64] $ /bin/bash -xe /tmp/jenkins4889443385421125569.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror epel-el6 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

Build failed in Jenkins: system-sync_mirrors-fedora-base-fcraw-x86_64 #189
by jenkins＠jenkins.phx.ovirt.org 07 Dec '17

07 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fcraw-x86_64/1…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fcraw-x86_64/w…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 Commit message: "ovirt-wgt: Exclude Fedora in 4.2 branch" > git rev-list bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 # timeout=10 [system-sync_mirrors-fedora-base-fcraw-x86_64] $ /bin/bash -xe /tmp/jenkins2492263899277715568.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror fedora-base-fcraw x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Resyncing repo: fedora-base-fcraw Syncing yum repo fedora-base-fcraw for arch: x86_64 fedora-base-fcraw/group 37% [=====- ] 0.0 B/s | 696 kB --:-- ETA fedora-base-fcraw/group | 1.8 MB 00:00 gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch.r FAILED gold-2.1.12.2-24.fc27.noar 0% [ ] 0.0 B/s | 0 B --:-- ETA gold-2.1.12.2-24.fc27.noarch: [Errno 256] No more mirrors to try. Build step 'Execute shell' marked build as failure

1 2

[ANN] oVirt 4.2.0 First Candidate Release is now available for testing
by Sandro Bonazzola 07 Dec '17

07 Dec '17

The oVirt Project is pleased to announce the availability of the First Candidate Release of oVirt 4.2.0, as of December 5th, 2017 This is pre-release software. This pre-release should not to be used in production. Please take a look at our community page[1] to learn how to ask questions and interact with developers and users. All issues or bugs should be reported via oVirt Bugzilla[2]. This update is the first candidate release of the 4.2.0 version. This release brings more than 280 enhancements and more than one thousand bug fixes, including more than 500 high or urgent severity fixes, on top of oVirt 4.1 series. What's new in oVirt 4.2.0? - The Administration Portal has been completely redesigned using Patternfly, a widely adopted standard in web application design. It now features a cleaner, more intuitive design, for an improved user experience. - There is an all-new VM Portal for non-admin users. - A new High Performance virtual machine type has been added to the New VM dialog box in the Administration Portal. - Open Virtual Network (OVN) adds support for Open vSwitch software defined networking (SDN). - oVirt now supports Nvidia vGPU. - The ovirt-ansible-roles set of packages help users with common administration tasks. - Virt-v2v now supports Debian/Ubuntu based VMs. For more information about these and other features, check out the oVirt 4.2.0 blog post <https://ovirt.org/blog/2017/11/introducing-ovirt-4.2.0-beta/> and stay tuned for further blog post. This release is available now on x86_64 architecture for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later This release supports Hypervisor Hosts on x86_64 and ppc64le architectures for: * Red Hat Enterprise Linux 7.4 or later * CentOS Linux (or similar) 7.4 or later * oVirt Node 4.2 (available for x86_64 only) See the release notes draft [3] for installation / upgrade instructions and a list of new features and bugs fixed. Notes: - oVirt Appliance is already available. - oVirt Node is already available [4] Additional Resources: * Read more about the oVirt 4.2.0 release highlights: http://www.ovirt.org/release/4.2.0/ * Get more oVirt project updates on Twitter: https://twitter.com/ovirt * Check out the latest project news on the oVirt blog: http://www.ovirt.org/blog/ [1] https://www.ovirt.org/community/ [2] https://bugzilla.redhat.com/enter_bug.cgi?classification=oVirt [3] http://www.ovirt.org/release/4.2.0/ [4] http://resources.ovirt.org/pub/ovirt-4.2-pre/iso/ -- SANDRO BONAZZOLA ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D Red Hat EMEA <https://www.redhat.com/> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

2 1

[JIRA] (OVIRT-1796) Re: Change in ovirt-wgt[ovirt-wgt-4.2]: packaging: Handle release suffix
by Daniel Belenky (oVirt JIRA) 07 Dec '17

07 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1796?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-1796: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Re: Change in ovirt-wgt[ovirt-wgt-4.2]: packaging: Handle release suffix > ------------------------------------------------------------------------ > > Key: OVIRT-1796 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1796 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: Daniel Belenky > > On Wed, Dec 6, 2017 at 5:15 PM, Code Review <gerrit(a)ovirt.org> wrote: > > Jenkins CI posted comments on this change. > > > > View Change > > > > Patch set 1:Continuous-Integration -1 > > > > Build Failed > > > > http://jenkins.ovirt.org/job/ovirt-wgt_4.2_check-patch-fc24-x86_64/2/ : > > FAILURE > AFAICT ovirt-wgt-standard.yaml says to exclude fc24 from 4.2 branch builds, > can someone please check this? > I already noticed that differences.html didn't show any differences > on the jenkins builds of my patch to do this: > https://gerrit.ovirt.org/85113 > I asked Sandro and he said if should be ok. Now I am not sure. > Thanks, > > > > http://jenkins.ovirt.org/job/ovirt-wgt_4.2_check-patch-el7-x86_64/3/ : > > SUCCESS > > > > To view, visit change 85156. To unsubscribe, visit settings. > > > > Gerrit-Project: ovirt-wgt > > Gerrit-Branch: ovirt-wgt-4.2 > > Gerrit-MessageType: comment > > Gerrit-Change-Id: Ie6f0680ec0e9d02ea660ed150fcfb5f9317a149e > > Gerrit-Change-Number: 85156 > > Gerrit-PatchSet: 1 > > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > > Gerrit-Reviewer: Jenkins CI > > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > > Gerrit-Reviewer: Rafael Martins <rafael(a)rafaelmartins.eng.br> > > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > > Gerrit-Comment-Date: Wed, 06 Dec 2017 15:15:02 +0000 > > Gerrit-HasComments: No > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[CQ]: 85140,2 (imgbased) failed "ovirt-master" system tests
by oVirt Jenkins 07 Dec '17

07 Dec '17

Change 85140,2 (imgbased) 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/85140/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4319/

1 0

[CQ]: 85157, 2 (ovirt-wgt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Dec '17

07 Dec '17

A system test invoked by the "ovirt-4.2" change queue including change 85157,2 (ovirt-wgt) failed. However, this change seems not to be the root cause for this failure. Change 85109,3 (ovirt-wgt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85109,3 (ovirt-wgt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85157/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85109/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/149/

1 0

[CQ]: 85156, 2 (ovirt-wgt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Dec '17

07 Dec '17

A system test invoked by the "ovirt-4.2" change queue including change 85156,2 (ovirt-wgt) failed. However, this change seems not to be the root cause for this failure. Change 85109,3 (ovirt-wgt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85109,3 (ovirt-wgt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85156/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85109/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/147/

1 0

[CQ]: 85155, 2 (ovirt-wgt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Dec '17

07 Dec '17

A system test invoked by the "ovirt-4.2" change queue including change 85155,2 (ovirt-wgt) failed. However, this change seems not to be the root cause for this failure. Change 85109,3 (ovirt-wgt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85109,3 (ovirt-wgt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85155/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85109/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/144/

1 0

[CQ]: 85154, 2 (ovirt-wgt) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Dec '17

07 Dec '17

A system test invoked by the "ovirt-4.2" change queue including change 85154,2 (ovirt-wgt) failed. However, this change seems not to be the root cause for this failure. Change 85109,3 (ovirt-wgt) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85109,3 (ovirt-wgt) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85154/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85109/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/141/

1 0

[CQ]: 85109,3 (ovirt-wgt) failed "ovirt-4.2" system tests
by oVirt Jenkins 07 Dec '17

07 Dec '17

Change 85109,3 (ovirt-wgt) is probably the reason behind recent system test failures in the "ovirt-4.2" 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/85109/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/138/

1 0

[JIRA] (OVIRT-1796) Re: Change in ovirt-wgt[ovirt-wgt-4.2]: packaging: Handle release suffix
by Yedidyah Bar David (oVirt JIRA) 06 Dec '17

06 Dec '17

Yedidyah Bar David created OVIRT-1796: ----------------------------------------- Summary: Re: Change in ovirt-wgt[ovirt-wgt-4.2]: packaging: Handle release suffix Key: OVIRT-1796 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1796 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra On Wed, Dec 6, 2017 at 5:15 PM, Code Review <gerrit(a)ovirt.org> wrote: > Jenkins CI posted comments on this change. > > View Change > > Patch set 1:Continuous-Integration -1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-wgt_4.2_check-patch-fc24-x86_64/2/ : > FAILURE AFAICT ovirt-wgt-standard.yaml says to exclude fc24 from 4.2 branch builds, can someone please check this? I already noticed that differences.html didn't show any differences on the jenkins builds of my patch to do this: https://gerrit.ovirt.org/85113 I asked Sandro and he said if should be ok. Now I am not sure. Thanks, > > http://jenkins.ovirt.org/job/ovirt-wgt_4.2_check-patch-el7-x86_64/3/ : > SUCCESS > > To view, visit change 85156. To unsubscribe, visit settings. > > Gerrit-Project: ovirt-wgt > Gerrit-Branch: ovirt-wgt-4.2 > Gerrit-MessageType: comment > Gerrit-Change-Id: Ie6f0680ec0e9d02ea660ed150fcfb5f9317a149e > Gerrit-Change-Number: 85156 > Gerrit-PatchSet: 1 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Rafael Martins <rafael(a)rafaelmartins.eng.br> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-Comment-Date: Wed, 06 Dec 2017 15:15:02 +0000 > Gerrit-HasComments: No -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

Build failed in Jenkins: system-sync_mirrors-fedora-base-fcraw-x86_64 #181
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-base-fcraw-x86_64/1…> ------------------------------------------ [...truncated 5.72 MB...] (55579/55720): python3-ccc 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-cccolutils-1.5-5.fc27. FAILED (55579/55720): python3-ccc 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python2-zeroconf-0.19.1-2.fc27 FAILED (55579/55720): ruby-gtksou 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-PyPDF2-1.26.0-2.fc27.n FAILED (55579/55720): ruby-gtksou 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-gtksourceview2-0.90.4-7.f FAILED (55579/55720): ruby-gtksou 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rsibreak-0.12.6-3.fc27.x86_64. FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-cligj-0.4.0-2.fc27.noa FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-libart2-devel-0.90.4-7.fc FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-Levenshtein-0.12.0-5.f FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-CFPropertyList-doc-2.3 FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-XStatic-Bootstrap-SCSS FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-cloud-sptheme-1.7.1-4. FAILED (55579/55720): python3-clo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-gnome2-0.90.4-7.fc27.5.x8 FAILED (55579/55720): ruby-gnome2 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubberband-devel-1.8.1-11.fc27 FAILED (55579/55720): rubberband- 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-proxifier-1.0.3-3.fc27 FAILED (55579/55720): ruby-gtkgle 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python2-zope-proxy-4.2.0-3.fc2 FAILED (55579/55720): ruby-gtkgle 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-tk-0.2.0-1.fc27.x86_64 FAILED (55579/55720): ruby-gtkgle 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-gtkglext-0.90.4-7.fc27.5. FAILED (55579/55720): ruby-gtkgle 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-gconf2-devel-0.90.4-7.fc2 FAILED (55579/55720): ruby-bonobo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-IPy-0.81-20.fc27.noarc FAILED (55579/55720): ruby-bonobo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA keybinder3-devel-0.3.2-3.fc27. FAILED (55579/55720): ruby-bonobo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-bonobo2-0.90.4-7.fc27.5.x FAILED (55579/55720): ruby-bonobo 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-aws-0.8.1-15.fc27.noarch. FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-ssh-gateway-doc-1. FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-adapt-0.3.0-2.fc27.noa FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rtfilter-1.1-5.fc27.x86_64.rpm FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-ZODB3-3.11.0-7.fc27.no FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-allison-2.0.3-16.fc27. FAILED (55579/55720): rubygem-all 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-progressbar-0.21.0-5.f FAILED (55579/55720): rubygem-pro 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-prawn-templates-doc-0. FAILED (55579/55720): rubygem-pra 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-abrt-doc-0.3.0-2.fc27. FAILED (55579/55720): rubygem-abr 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-citeproc-py-0.3.0-7.fc FAILED (55579/55720): python3-cit 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-Pyped-1.4-7.fc27.noarc FAILED (55579/55720): python3-con 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-concurrentloghandler-0 FAILED (55579/55720): python3-con 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rst2pdf-0.93-10.fc27.noarch.rp FAILED (55579/55720): rst2pdf-0.9 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-activeldap-doc-4.0.6-3 FAILED (55579/55720): rubygem-net 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-ping-doc-1.7.7-4.f FAILED (55579/55720): rubygem-net 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-Platform-doc-0.4.0-12. FAILED (55579/55720): ruby-libgla 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-libglade2-0.90.4-7.fc27.5 FAILED (55579/55720): ruby-libgla 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-deep_merge-1.1.1-2.fc2 FAILED (55579/55720): rubygem-com 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rtl-sdr-0.5.3-10.fc27.i686.rpm FAILED (55579/55720): rubygem-com 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-occi-cli-doc-4.3.10-1. FAILED (55579/55720): rubygem-com 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-compass-rails-doc-2.0. FAILED (55579/55720): rubygem-com 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-openscap-0.4.7-3.fc27. FAILED (55579/55720): rubygem-sim 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-openbabel-2.4.1-8.fc27.x8 FAILED (55579/55720): rubygem-sim 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-Traits-4.5.0-15.gitac5 FAILED (55579/55720): rubygem-sim 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-simple-rss-1.3.1-3.fc2 FAILED (55579/55720): rubygem-sim 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-XStatic-termjs-0.0.7.0 FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-sprockets-doc-3.7.1-3. FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-oauth-0.5.1-2.fc27.noa FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-RubyInline-3.11.3-10.f FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-turbolinks-5.0.1-3.fc2 FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rsvndump-0.6-11.fc27.x86_64.rp FAILED (55579/55720): rsvndump-0. 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-dns-0.8.0-3.fc27.n FAILED (55579/55720): rubygem-net 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-XStatic-jquery-ui-1.10 FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-afm-doc-0.2.2-6.fc27.n FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-ping-1.7.7-4.fc27. FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-parse-cron-doc-0.1.4-6 FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-http-persistent-2. FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA python3-collectd-ceilometer-pl FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-ansi-doc-1.5.0-5.fc27. FAILED (55579/55720): rubygem-ans 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-taglib-1.1-16.fc27.noarch FAILED (55579/55720): rubygem-unf 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-session-3.1.0-12.fc25. FAILED (55579/55720): rubygem-unf 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-unf-doc-0.1.4-9.fc27.n FAILED (55579/55720): rubygem-unf 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-opengl-doc-0.10.0-3.fc FAILED (55579/55720): rubygem-spr 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rtaudio-devel-4.0.11-13.fc27.i FAILED (55579/55720): rubygem-spr 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-sprockets-rails-doc-3. FAILED (55579/55720): rubygem-spr 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-uglifier-doc-3.2.0-2.f FAILED (55579/55720): rubygem-thi 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-turbolinks-doc-5.0.1-3 FAILED (55579/55720): rubygem-thi 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-thin-doc-1.7.2-4.fc27. FAILED (55579/55720): rubygem-thi 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-nio4r-2.1.0-4.fc27.x86 FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA ruby-shogun-6.0.0-5.fc27.x86_6 FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-shoulda-doc-3.5.0-3.fc FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-net-ssh-doc-4.1.0-2.fc FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-activeldap-4.0.6-3.fc2 FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-syck-doc-1.0.5-8.fc27. FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-sinatra-rabbit-doc-1.1 FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-parse-cron-0.1.4-6.fc2 FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-daemons-doc-1.1.9-7.fc FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-picnic-0.8.1-10.fc21.n FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-webmock-doc-2.3.2-2.fc FAILED (55579/55720): rubygem-web 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-sexp_processor-doc-4.7 FAILED (55579/55720): rubygem-pra 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-prawn-templates-0.0.4- FAILED (55579/55720): rubygem-pra 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-occi-api-doc-4.3.14-1. FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-connection_pool-doc-2. FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-coveralls-0.8.13-4.fc2 FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-semantic-1.6.0-3.fc27. FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-parallel-doc-1.3.3-5.f FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-narray-devel-0.6.1.1-8 FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-shellany-0.0.1-4.fc27. FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-virtus-1.0.5-1.fc23.no FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-parseconfig-doc-1.0.8- FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-origin-2.2.0-3.fc27.no FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-syntax-1.2.0-5.fc27.no FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-text-format-1.0.0-13.f FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-treetop-1.6.3-4.fc27.n FAILED (55579/55720): rubygem-tre 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-serialport-1.3.1-11.fc FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-taskjuggler-doc-3.5.0- FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-thread_safe-doc-0.3.6- FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-vcr-2.3.0-9.fc27.noarc FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-sinatra-doc-2.0.0-2.fc FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-simplecov-0.13.0-3.fc2 FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-tk-0.2.0-1.fc27.x86_64 FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-settingslogic-2.0.9-8. FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-proxifier-1.0.3-3.fc27 FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-shoulda-context-1.2.2- FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-test_declarative-doc-0 FAILED (55579/55720): rubygem-tes 99% [===============-] 559 kB/s | 44 GB 00:47 ETA rubygem-occi-api-doc-4.3.14-1.fc27.noarch: [Errno 256] No more mirrors to try. python3-cligj-0.4.0-2.fc27.noarch: [Errno 256] No more mirrors to try. python3-celery-4.0.2-3.fc27.noarch: [Errno 256] No more mirrors to try. ruby-gtksourceview2-0.90.4-7.fc27.5.x86_64: [Errno 256] No more mirrors to try. kf5-audiocd-kio-devel-17.04.1-1.fc27.i686: [Errno 256] No more mirrors to try. python2-xlrd-1.0.0-6.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-connection_pool-doc-2.2.0-2.fc24.noarch: [Errno 256] No more mirrors to try. rubygem-prawn-templates-0.0.4-3.fc27.noarch: [Errno 256] No more mirrors to try. keybinder3-0.3.2-3.fc27.x86_64: [Errno 256] No more mirrors to try. rt-tests-4.4.2-1.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-cucumber-wire-0.0.1-4.fc27.noarch: [Errno 256] No more mirrors to try. kde-style-phase-15.08.3-5.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-allison-2.0.3-16.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-RubyInline-3.11.3-10.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-deep_merge-1.1.1-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-afm-doc-0.2.2-6.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-coveralls-0.8.13-4.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-oauth-0.5.1-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-proxifier-1.0.3-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-text-format-1.0.0-13.fc22.noarch: [Errno 256] No more mirrors to try. rubygem-semantic-1.6.0-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-turbolinks-5.0.1-3.fc27.noarch: [Errno 256] No more mirrors to try. keyutils-libs-devel-1.5.10-3.fc27.i686: [Errno 256] No more mirrors to try. rubygem-daemons-doc-1.1.9-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-uglifier-doc-3.2.0-2.fc27.noarch: [Errno 256] No more mirrors to try. rtaudio-devel-4.0.11-13.fc27.i686: [Errno 256] No more mirrors to try. kde-plasma-activitymanager-0.5-8.fc22.x86_64: [Errno 256] No more mirrors to try. python3-APLpy-1.1.1-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-parse-cron-doc-0.1.4-6.fc27.noarch: [Errno 256] No more mirrors to try. ruby-libart2-devel-0.90.4-7.fc27.5.i686: [Errno 256] No more mirrors to try. rubygem-syck-doc-1.0.5-8.fc27.noarch: [Errno 256] No more mirrors to try. rst2pdf-0.93-10.fc27.noarch: [Errno 256] No more mirrors to try. rsvndump-0.6-11.fc27.x86_64: [Errno 256] No more mirrors to try. python3-XStatic-Rickshaw-1.5.0.0-11.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-sexp_processor-doc-4.7.0-3.fc27.noarch: [Errno 256] No more mirrors to try. python2-zope-testing-4.6.1-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-taskjuggler-doc-3.5.0-1.fc22.noarch: [Errno 256] No more mirrors to try. rubygem-Platform-doc-0.4.0-12.fc27.noarch: [Errno 256] No more mirrors to try. ruby-ncurses-1.3.1-22.fc27.x86_64: [Errno 256] No more mirrors to try. python3-XStatic-Jasmine-2.4.1.1-1.fc27.noarch: [Errno 256] No more mirrors to try. ruby-taglib-1.1-16.fc27.noarch: [Errno 256] No more mirrors to try. ruby-gnome2-0.90.4-7.fc27.5.x86_64: [Errno 256] No more mirrors to try. ruby-aws-0.8.1-15.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-sinatra-rabbit-doc-1.1.6-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-session-3.1.0-12.fc25.noarch: [Errno 256] No more mirrors to try. rubygem-treetop-1.6.3-4.fc27.noarch: [Errno 256] No more mirrors to try. rtfilter-1.1-5.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-test_declarative-doc-0.0.5-12.fc27.noarch: [Errno 256] No more mirrors to try. ruby-libglade2-0.90.4-7.fc27.5.x86_64: [Errno 256] No more mirrors to try. python2-xlwt-1.1.2-3.fc27.noarch: [Errno 256] No more mirrors to try. python3-cccolutils-1.5-5.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-net-ssh-doc-4.1.0-2.fc27.noarch: [Errno 256] No more mirrors to try. kdegames3-devel-3.5.10-24.fc26.i686: [Errno 256] No more mirrors to try. python3-IPy-0.81-20.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-settingslogic-2.0.9-8.fc27.noarch: [Errno 256] No more mirrors to try. python2-zope-component-4.3.0-4.fc27.noarch: [Errno 256] No more mirrors to try. kdegames3-devel-3.5.10-24.fc26.x86_64: [Errno 256] No more mirrors to try. rubygem-thin-doc-1.7.2-4.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-net-ping-doc-1.7.7-4.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-thread_safe-doc-0.3.6-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-prawn-templates-doc-0.0.4-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-serialport-1.3.1-11.fc27.x86_64: [Errno 256] No more mirrors to try. python2-zope-contenttype-4.1.0-8.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-parseconfig-doc-1.0.8-2.fc27.noarch: [Errno 256] No more mirrors to try. ruby-shogun-6.0.0-5.fc27.x86_64: [Errno 256] No more mirrors to try. rt-mailgate-4.4.2-1.fc27.noarch: [Errno 256] No more mirrors to try. rsibreak-0.12.6-3.fc27.x86_64: [Errno 256] No more mirrors to try. 1:rubygem-sinatra-doc-2.0.0-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-net-ssh-gateway-doc-1.2.0-8.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-unf-doc-0.1.4-9.fc27.noarch: [Errno 256] No more mirrors to try. electronics-menu-1.0-18.fc27.noarch: [Errno 256] No more mirrors to try. python3-PyLink-0.3.2-6.fc27.noarch: [Errno 256] No more mirrors to try. python3-Pyped-1.4-7.fc27.noarch: [Errno 256] No more mirrors to try. python3-ZODB3-3.11.0-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-ansi-doc-1.5.0-5.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-tk-0.2.0-1.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-compass-rails-doc-2.0.4-4.fc27.noarch: [Errno 256] No more mirrors to try. ruby-gtkglext-0.90.4-7.fc27.5.x86_64: [Errno 256] No more mirrors to try. kf5-kdgantt2-16.08.3-4.fc27.i686: [Errno 256] No more mirrors to try. rubygem-virtus-1.0.5-1.fc23.noarch: [Errno 256] No more mirrors to try. keybinder3-devel-0.3.2-3.fc27.i686: [Errno 256] No more mirrors to try. python3-cmigemo-0.1.6-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-turbolinks-doc-5.0.1-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-progressbar-0.21.0-5.fc27.noarch: [Errno 256] No more mirrors to try. ketchup-1.0.1-10.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-shoulda-doc-3.5.0-3.fc24.noarch: [Errno 256] No more mirrors to try. python3-XStatic-termjs-0.0.7.0-1.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-syntax-1.2.0-5.fc27.noarch: [Errno 256] No more mirrors to try. python3-citeproc-py-0.3.0-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-net-ping-1.7.7-4.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-sprockets-rails-doc-3.2.0-5.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-shellany-0.0.1-4.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-net-dns-0.8.0-3.fc27.noarch: [Errno 256] No more mirrors to try. python3-PyPDF2-1.26.0-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-narray-devel-0.6.1.1-8.fc27.x86_64: [Errno 256] No more mirrors to try. python3-GridDataFormats-0.3.3-1.fc27.noarch: [Errno 256] No more mirrors to try. ruby-bonobo2-0.90.4-7.fc27.5.x86_64: [Errno 256] No more mirrors to try. rubygem-origin-2.2.0-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-activeldap-doc-4.0.6-3.fc27.noarch: [Errno 256] No more mirrors to try. python3-cclib-1.3.2-7.fc27.noarch: [Errno 256] No more mirrors to try. 1:kde-workspace-devel-4.11.22-20.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-abrt-doc-0.3.0-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-vcr-2.3.0-9.fc27.noarch: [Errno 256] No more mirrors to try. python3-cloud-sptheme-1.7.1-4.fc27.noarch: [Errno 256] No more mirrors to try. ruby-gconf2-devel-0.90.4-7.fc27.5.i686: [Errno 256] No more mirrors to try. ruby-openbabel-2.4.1-8.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-parse-cron-0.1.4-6.fc27.noarch: [Errno 256] No more mirrors to try. rubberband-devel-1.8.1-11.fc27.i686: [Errno 256] No more mirrors to try. python3-Traits-4.5.0-15.gitac5d029.fc27.x86_64: [Errno 256] No more mirrors to try. kde-plasma-publictransport-libs-0.10-0.18.20111204git.fc27.x86_64: [Errno 256] No more mirrors to try. python3-PyMySQL-0.7.11-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-webmock-doc-2.3.2-2.fc27.noarch: [Errno 256] No more mirrors to try. rubberband-devel-1.8.1-11.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-CFPropertyList-doc-2.3.3-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-sprockets-doc-3.7.1-3.fc27.noarch: [Errno 256] No more mirrors to try. python2-zope-i18nmessageid-4.0.3-10.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-simple-rss-1.3.1-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-activeldap-4.0.6-3.fc27.noarch: [Errno 256] No more mirrors to try. rsync-daemon-3.1.2-7.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-simplecov-0.13.0-3.fc27.noarch: [Errno 256] No more mirrors to try. python3-collectd-ceilometer-plugin-1.0.1-2.fc27.noarch: [Errno 256] No more mirrors to try. python2-zeroconf-0.19.1-2.fc27.noarch: [Errno 256] No more mirrors to try. python3-Levenshtein-0.12.0-5.fc27.x86_64: [Errno 256] No more mirrors to try. kf5-audiocd-kio-17.04.1-1.fc27.i686: [Errno 256] No more mirrors to try. python3-Pympler-0.4.3-6.fc27.noarch: [Errno 256] No more mirrors to try. kde-plasma-ihatethecashew-0.4-15.fc27.x86_64: [Errno 256] No more mirrors to try. rubygem-shoulda-context-1.2.2-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-net-http-persistent-2.9.4-8.fc27.noarch: [Errno 256] No more mirrors to try. python3-CommonMark-0.7.2-5.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-occi-cli-doc-4.3.10-1.fc27.noarch: [Errno 256] No more mirrors to try. python3-adapt-0.3.0-2.fc27.noarch: [Errno 256] No more mirrors to try. kde-style-phase-15.08.3-5.fc27.i686: [Errno 256] No more mirrors to try. python3-XStatic-Bootstrap-SCSS-3.3.7.1-2.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-opengl-doc-0.10.0-3.fc27.noarch: [Errno 256] No more mirrors to try. python3-concurrentloghandler-0.9.1-5.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-openscap-0.4.7-3.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-parallel-doc-1.3.3-5.fc27.noarch: [Errno 256] No more mirrors to try. rtl-sdr-0.5.3-10.fc27.i686: [Errno 256] No more mirrors to try. rubygem-picnic-0.8.1-10.fc21.noarch: [Errno 256] No more mirrors to try. python2-zope-proxy-4.2.0-3.fc27.x86_64: [Errno 256] No more mirrors to try. python3-XStatic-jquery-ui-1.10.4.1-8.fc27.noarch: [Errno 256] No more mirrors to try. rubygem-nio4r-2.1.0-4.fc27.x86_64: [Errno 256] No more mirrors to try. Build step 'Execute shell' marked build as failure

1 6

Build failed in Jenkins: system-sync_mirrors-fedora-updates-fc25-x86_64 #884
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-fedora-updates-fc25-x86_64…> ------------------------------------------ [...truncated 17.17 MB...] 6:texlive-soton-doc-svn16215.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-log-encoder-msgpack-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-mciteplus-svn31648.1.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-biblatex-publist-doc-svn41812-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-cellspace-doc-svn15878.1.6-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-yhmath-svn31155.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-router-radius-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-sansmathaccent-svn30187.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-kotex-utils-doc-svn38727-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-boxedminipage-svn17087.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-musixtnt-doc-svn40307-33.fc25.1.noarch: [Errno 256] No more mirrors to try. urjtag-0.10-13.fc25.20111215gite1a4227.x86_64: [Errno 256] No more mirrors to try. wine-twain-2.19-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-xpicture-svn28770.1.2a-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-lilyglyphs-doc-svn33164.0.2.3-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-datetime2-icelandic-doc-svn36692.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-multidef-svn40637-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-wsemclassic-svn31532.1.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ebook-svn29466.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mathcomp-doc-svn15878.0.1f-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-capt-of-doc-svn29803.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-exp-testopt-svn15878.0.3-33.fc25.1.noarch: [Errno 256] No more mirrors to try. unity-gtk2-module-0.0.0+17.04.20170403-1.fc25.i686: [Errno 256] No more mirrors to try. 6:texlive-hyper-doc-svn17357.4.2d-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-gcard-doc-svn15878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-plugin-zergpool-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-bibleref-mouth-doc-svn25527.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-uiucredborder-doc-svn29974.1.00-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-flashcards-doc-svn19667.1.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-uassign-svn38459-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-texmate-doc-svn15878.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-sphack-svn20842.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-syllogism-doc-svn15878.1.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. why3-examples-0.87.3-1.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-sasnrdisplay-doc-svn33120.0.93-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mailing-doc-svn15878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-sourcesanspro-doc-svn37379.2.5-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-warning-svn22028.0.01-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-colorwav-doc-svn15878.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-biblatex-anonymous-svn42152-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-minifp-doc-svn32559.0.96-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-biblatex-realauthor-svn42072-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-xwatermark-svn28090.1.5.2d-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-cell-doc-svn20756.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fontch-svn17859.2.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mandi-svn40050-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-syntrace-svn15878.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-tabulary-svn34368.0.10-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-context-gantt-svn27472.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-luaxml-svn32741.0.0.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-srcredact-bin-svn38710-33.20160520.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-pst-exa-svn35248.0.05-33.fc25.1.noarch: [Errno 256] No more mirrors to try. why3-xemacs-0.87.3-1.fc25.noarch: [Errno 256] No more mirrors to try. wingpanel-devel-2.0.4-1.fc25.i686: [Errno 256] No more mirrors to try. 6:texlive-datetime2-estonian-svn36682.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. wxGTK3-3.0.3-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-gauss-svn32934.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-uestcthesis-svn36371.1.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. wine-courier-fonts-2.19-1.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-fetamont-doc-svn38746-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-schemata-svn39510-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-scheme-basic-svn25923.0-33.20160520.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ccfonts-doc-svn17122.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-menukeys-svn40599-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-hyper-svn17357.4.2d-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-xtab-doc-svn23347.2.3f-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-match_parens-doc-svn36270.1.43-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-foreign-svn27819.2.7-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-gcite-svn15878.1.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-libris-svn19409.1.007-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-xkeyval-doc-svn35741.2.7a-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-exsol-svn41377-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-units-doc-svn36944.0.9b-33.fc25.1.noarch: [Errno 256] No more mirrors to try. x2goserver-4.0.1.20-1.fc25.x86_64: [Errno 256] No more mirrors to try. uwsgi-plugin-coroae-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. wine-mono-4.7.1-1.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-pst-platon-doc-svn16538.0.01-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-memdesign-doc-svn34157.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mugsthesis-doc-svn34878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. vim-omnicppcomplete-0.41-8.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-luatex85-svn41395-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fontinst-doc-svn40768-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ydoc-doc-svn26202.0.6alpha-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ucdavisthesis-doc-svn40772-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uhd-3.10.1.0-1.fc25.i686: [Errno 256] No more mirrors to try. 6:texlive-biblatex-philosophy-svn41482-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-lapdf-doc-svn23806.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mtgreek-doc-svn17967.1.1+-33.fc25.1.noarch: [Errno 256] No more mirrors to try. voms-mysql-plugin-3.1.7-5.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-exceltex-doc-svn26313.0.5.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-bosisio-doc-svn16989.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-flashmovie-svn25768.0.4-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-marginfix-doc-svn31598.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fonttable-doc-svn21399.1.6b-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-hobby-doc-svn39793-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ftnxtra-doc-svn29652.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mfware-bin-svn40473-33.20160520.fc25.1.x86_64: [Errno 256] No more mirrors to try. xcb-util-xrm-devel-1.2-1.fc25.i686: [Errno 256] No more mirrors to try. 6:texlive-fc-svn32796.1.4-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-logger-redis-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-mathcomp-svn15878.0.1f-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fmp-doc-svn15878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-xetex-def-svn40327-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-spreadtab-svn35531.0.4c-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mintspirit-doc-svn32069.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-lstaddons-doc-svn26196.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-biblatex-chem-doc-svn42065-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-eledmac-svn38639-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-wallpaper-svn15878.1.10-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-datetime2-lsorbian-doc-svn36692.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-pst-infixplot-doc-svn15878.0.11-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-flacards-doc-svn19440.0.1.1b-33.fc25.1.noarch: [Errno 256] No more mirrors to try. tiled-plugin-python-0.18.2-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-fullminipage-doc-svn34545.0.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ryethesis-svn33945.1.36-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-texdoc-doc-svn40768-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-envlab-svn15878.1.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. tigervnc-license-1.8.0-1.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-xyling-svn15878.1.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-plugin-rpc-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-faktor-doc-svn15878.0.1b-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-thesis-titlepage-fhac-doc-svn15878.0.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. wildfly-doc-10.1.0-10.fc25.noarch: [Errno 256] No more mirrors to try. 6:texlive-fp-svn15878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fpl-doc-svn15878.1.002-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-wrapfig-svn22048.3.6-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-cm-svn32865.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-sphdthesis-svn34374.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-metre-svn18489.1.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-epigrafica-svn17210.1.01-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mathdesign-svn31639.2.31-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-elements-doc-svn41161-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-featpost-doc-svn35346.0.8.8-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-mflogo-svn38628-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-epsincl-svn29349.0.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-marginnote-doc-svn41382-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-lshort-vietnamese-doc-svn15878.4.00-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-xetex-doc-svn41438-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-storecmd-svn24431.0.0.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-hyphen-churchslavonic-svn41113-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-chicago-svn15878.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-jfontmaps-svn40613-33.fc25.1.noarch: [Errno 256] No more mirrors to try. uwsgi-logger-crypto-2.0.15-1.fc25.x86_64: [Errno 256] No more mirrors to try. 6:texlive-fancyhdr-svn15878.3.1-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-fouriernc-doc-svn29646.0-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-zlmtt-svn34485.1.01-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-ushort-doc-svn32261.2.2-33.fc25.1.noarch: [Errno 256] No more mirrors to try. 6:texlive-tfrupee-doc-svn20770.1.02-33.fc25.1.noarch: [Errno 256] No more mirrors to try. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-biblatex-swiss-legal-doc-svn32750.1.1.2a-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-biblatex-swiss-legal-doc-svn32750.1.1.2a-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-bibtex8-bin-svn40473-33.20160520.fc25.1.x86_64.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-bibtopicprefix-doc-svn15878.1.10-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-bibtopicprefix-doc-svn15878.1.10-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-bizcard-svn15878.1.1-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-bizcard-svn15878.1.1-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-charter-svn15878.0-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-charter-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-chbibref-svn17120.1.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-chbibref-svn17120.1.0-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-chivo-doc-svn40931-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-chkfloat-svn27473.0.1-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-chkfloat-svn27473.0.1-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-cleanthesis-doc-svn38221.0.3.1-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-cleanthesis-doc-svn38221.0.3.1-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-clearsans-svn34405.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-clearsans-svn34405.0-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-comprehensive-doc-svn38992-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-cstex-doc-svn41301-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-cstex-doc-svn41301-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-enumitem-doc-svn24146.3.5.2-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-enumitem-doc-svn24146.3.5.2-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-fandol-doc-svn37889.0.3-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-fandol-doc-svn37889.0.3-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-graphbox-doc-svn35075.1.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-hfoldsty-svn29349.1.15-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 42270720 type 42336256 offset -42401792 count 42467328 Removing texlive-hfoldsty-svn29349.1.15-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-impatient-doc-svn35573.0-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-impatient-doc-svn35573.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-iopart-num-svn15878.2.1-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-iopart-num-svn15878.2.1-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-jslectureplanner-doc-svn41043-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-jslectureplanner-doc-svn41043-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-kerkis-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-luatexbase-doc-svn38550-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-luatexbase-doc-svn38550-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-mailing-doc-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-musixtex-svn41352-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-musixtex-svn41352-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-newtx-svn40165-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-newtx-svn40165-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-newtx-doc-svn40165-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-newtx-doc-svn40165-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-nih-doc-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-nimbus15-svn39343-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-nimbus15-svn39343-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-pageslts-doc-svn39164-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-pageslts-doc-svn39164-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-petri-nets-svn39165-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-petri-nets-svn39165-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-pgf-blur-doc-svn31693.1.01-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-pgf-blur-doc-svn31693.1.01-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-pgf-doc-svn40966-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-pst-cox-svn15878.0.98_Beta-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-pst-cox-svn15878.0.98_Beta-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-pst-electricfield-doc-svn29803.0.14-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-pst-electricfield-doc-svn29803.0.14-33.fc25.1.noarch.rpm due to failed signature check. Removing texlive-schwalbe-chess-doc-svn39318-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-sty2dtx-doc-svn29743.2.3-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-sty2dtx-doc-svn29743.2.3-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-texcount-doc-svn31323.3.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-texcount-doc-svn31323.3.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-titlesec-doc-svn40129-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-titlesec-doc-svn40129-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-toolbox-doc-svn32260.5.1-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-toolbox-doc-svn32260.5.1-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-tools-doc-svn40934-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-tools-doc-svn40934-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-turabian-formatting-svn40065-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-turabian-formatting-svn40065-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-turkmen-svn17748.0.2-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-turkmen-svn17748.0.2-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-turkmen-doc-svn17748.0.2-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-turkmen-doc-svn17748.0.2-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-uiucredborder-doc-svn29974.1.00-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-uiucredborder-doc-svn29974.1.00-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-utf8mex-doc-svn15878.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-utf8mex-doc-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-utopia-svn15878.0-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-utopia-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-vlna-doc-svn40768-33.fc25.1.noarch.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing texlive-vlna-doc-svn40768-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-vntex-svn30579.3.2-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-vntex-svn30579.3.2-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-zapfchan-svn31835.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-zapfchan-svn31835.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/t/texlive-zwgetfdate-svn15878.0-33.fc25.1.noarch.rpm: headerRead failed: hdr load: BAD Removing texlive-zwgetfdate-svn15878.0-33.fc25.1.noarch.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/v/varnish-5.0.0-5.fc25.x86_64.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing varnish-5.0.0-5.fc25.x86_64.rpm due to failed signature check. Removing varnish-devel-5.0.0-5.fc25.i686.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/v/vips-devel-8.4.4-1.fc25.1.x86_64.rpm: headerRead failed: hdr load: BAD Removing vips-devel-8.4.4-1.fc25.1.x86_64.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/v/vkmark-2017.08-0.1.20170904git0fed663.fc25.x86_64.rpm: headerRead failed: region trailer: BAD, tag 0 type 0 offset 0 count 0 Removing vkmark-2017.08-0.1.20170904git0fed663.fc25.x86_64.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/x/xen-libs-4.7.3-8.fc25.i686.rpm: headerRead failed: hdr load: BAD Removing xen-libs-4.7.3-8.fc25.i686.rpm due to failed signature check. error: /var/www/html/repos/yum/fedora-updates-fc25/base/Packages/x/xen-licenses-4.7.3-8.fc25.x86_64.rpm: headerRead failed: hdr load: BAD Removing xen-licenses-4.7.3-8.fc25.x86_64.rpm due to failed signature check. Build step 'Execute shell' marked build as failure

1 5

[oVirt Jenkins] ovirt-appliance_ovirt-4.1-snapshot_build-artifacts-el7-x86_64 - Build # 364 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

------=_Part_278_1610545235.1512485606319 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build: http://jenkins.ovirt.org/job/ovirt-appliance_ovirt-4.1-snapshot_build-artif… Build Number: 364 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #364 [Daniel Belenky] Added germano(a)redhat.com to whitelist [Gal Ben Haim] kubevirt-ansible: Adding github pipeline [Martin Sivak] Cleanup the job for ovirt-optimizer [Yuval Turgeman] automation: view install log in console ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_278_1610545235.1512485606319--

1 1

[JIRA] (OVIRT-1795) add /tmp engine logs to be collected in ost
by Dafna Ron (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1795?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-1795: -------------------------------- Assignee: Dafna Ron (was: infra) > add /tmp engine logs to be collected in ost > ------------------------------------------- > > Key: OVIRT-1795 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1795 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Dafna Ron > > when engine fails to be deployed and there is nothing written in the engine log it would make debugging easier if we also collect the tmp logs created by engine, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1795) add /tmp engine logs to be collected in ost
by Dafna Ron (oVirt JIRA) 06 Dec '17

06 Dec '17

Dafna Ron created OVIRT-1795: -------------------------------- Summary: add /tmp engine logs to be collected in ost Key: OVIRT-1795 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1795 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra when engine fails to be deployed and there is nothing written in the engine log it would make debugging easier if we also collect the tmp logs created by engine, -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

Default assignee for bugzilla component
by Sahina Bose 06 Dec '17

06 Dec '17

Hi! Could you change the default assignee on Product: cockpit-ovirt Component:gdeploy to godas(a)redhat.com? thanks sahina

3 3

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Daniel Belenky (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512572024-12025-143 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1788: --------------------------------------- [~gshereme(a)redhat.com] I'll be happy to assist with that > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512572024-12025-143 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Daniel Belenky commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] I'll be happy to assist with that</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512572024-12025-143--

1 0

[CQ]: 85136,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 06 Dec '17

06 Dec '17

Change 85136,3 (ovirt-engine) 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/85136/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4313/

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- Ok -- I'll need your assistance setting it up. I have no idea how to pull them, start them, or cache them :) > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512568585-25653-223 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- [~gshereme(a)redhat.com] awesome! so we don`t need to make our own, just use theirs and make sure they are cached properly between runs... > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512568585-25653-223 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] awesome! so we don`t need to make our own, just use theirs and make sure they are cached properly between runs…</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512568585-25653-223--

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 06 Dec '17

06 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1793: ------------------------------------------- Assignee: Daniel Belenky (was: infra) > PHX repo mirror inconsistent > ---------------------------- > > Key: OVIRT-1793 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Daniel Belenky > > The [infra-docs_master_check-merged-el7-x86_64|http://jenkins.ovirt.org/job/infr…] job failed due to a missing RPM on the mirror that is present in the index: > 12:13:44 http://mirrors.phx.ovirt.org/repos/yum/epel-el7/base/f/fontawesome-fonts-4.…: [Errno 14] HTTP Error 404 - Not Found > We may need to fix this mirror or disable it for this job if this package is filtered out to conserve disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 06 Dec '17

06 Dec '17

This is a multi-part message in MIME format... ------------=_1512558689-17283-163 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- They provide containers already: https://github.com/SeleniumHQ/docker-selenium Can we use those somehow? > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512558689-17283-163 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Greg Sheremeta commented on OVIRT-1788:</h3> <p>They provide containers already: <a href="https://github.com/SeleniumHQ/docker-selenium">https://github.com/SeleniumHQ/docker-selenium</a></p> <p>Can we use those somehow?</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512558689-17283-163--

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1053
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 Commit message: "ovirt-wgt: Exclude Fedora in 4.2 branch" > git rev-list bd4aab54d0c2d8ee1df391e2bcc82634ff73ff01 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins4348173935222386919.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1

[CQ]: 85067, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Dec '17

06 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85067,3 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 85049,2 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85049,2 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85067/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85049/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4305/

1 0

[CQ]: 85067, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 06 Dec '17

06 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85067,3 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 85049,2 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85049,2 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85067/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85049/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4303/

1 0

[oVirt Jenkins] ovirt-system-tests_performance-suite-master - Build # 22 - Failure!
by jenkins＠jenkins.phx.ovirt.org 06 Dec '17

06 Dec '17

------=_Part_263_1882562675.1512441226520 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Project: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-= master/=20 Build: http://jenkins.ovirt.org/job/ovirt-system-tests_performance-suite-ma= ster/22/ Build Number: 22 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #22 [Yaniv Kaul] Set OvfUpdateIntervalInMinutes=3D10 for oVirt System Test suit= e. [Gal Ben Haim] kubevirt-ansible: Adding github pipeline [Martin Sivak] Cleanup the job for ovirt-optimizer ----------------- Failed Tests: ----------------- 1 tests failed. FAILED: 040_add_hosts_vms.verify_add_hosts Error Message: 1 hosts failed installation: lago-performance-suite-master-host-0: install_failed -------------------- >> begin captured logging << -------------------- ovirtlago.testlib: ERROR: * Unhandled exception in <function <lambda> a= t 0x4c31410> Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 298, in <lambda> lambda: _single_host_up(hosts_service, total_hosts) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 166, in _single_host_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 175, in _check_problematic_hosts raise RuntimeError(dump_hosts) RuntimeError: 1 hosts failed installation: lago-performance-suite-master-host-0: install_failed --------------------- >> end captured logging << --------------------- Stack Trace: File "/usr/lib64/python2.7/unittest/case.py", line 369, in run testMethod() File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTes= t self.test(*self.arg) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 129, i= n wrapped_test test() File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 59, in= wrapper return func(get_test_prefix(), *args, **kwargs) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 290, in verify_add_hosts verify_add_hosts_4(api) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 298, in verify_add_hosts_4 lambda: _single_host_up(hosts_service, total_hosts) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 271, i= n assert_true_within_long assert_equals_within_long(func, True, allowed_exceptions) File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 258, i= n assert_equals_within_long func, value, LONG_TIMEOUT, allowed_exceptions=3Dallowed_exceptions File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 219, i= n assert_equals_within res =3D func() File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 298, in <lambda> lambda: _single_host_up(hosts_service, total_hosts) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 166, in _single_host_up _check_problematic_hosts(hosts_service) File "/home/jenkins/workspace/ovirt-system-tests_performance-suite-master= /ovirt-system-tests/performance-suite-master/test-scenarios/040_add_hosts_v= ms.py", line 175, in _check_problematic_hosts raise RuntimeError(dump_hosts) '1 hosts failed installation:\nlago-performance-suite-master-host-0: instal= l_failed\n\n-------------------- >> begin captured logging << -------------= -------\novirtlago.testlib: ERROR: * Unhandled exception in <function <= lambda> at 0x4c31410>\nTraceback (most recent call last):\n File "/usr/lib= /python2.7/site-packages/ovirtlago/testlib.py", line 219, in assert_equals_= within\n res =3D func()\n File "/home/jenkins/workspace/ovirt-system-te= sts_performance-suite-master/ovirt-system-tests/performance-suite-master/te= st-scenarios/040_add_hosts_vms.py", line 298, in <lambda>\n lambda: _sin= gle_host_up(hosts_service, total_hosts)\n File "/home/jenkins/workspace/ov= irt-system-tests_performance-suite-master/ovirt-system-tests/performance-su= ite-master/test-scenarios/040_add_hosts_vms.py", line 166, in _single_host_= up\n _check_problematic_hosts(hosts_service)\n File "/home/jenkins/work= space/ovirt-system-tests_performance-suite-master/ovirt-system-tests/perfor= mance-suite-master/test-scenarios/040_add_hosts_vms.py", line 175, in _chec= k_problematic_hosts\n raise RuntimeError(dump_hosts)\nRuntimeError: 1 ho= sts failed installation:\nlago-performance-suite-master-host-0: install_fai= led\n\n--------------------- >> end captured logging << -------------------= --' ------=_Part_263_1882562675.1512441226520--

1 1

[CQ]: 85067, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '17

05 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85067,3 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 85049,2 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85049,2 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85067/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85049/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4299/

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512493937-23434-132 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- [~gshereme(a)redhat.com] I supposed Grid could be the solution we're looking for, if it has some kind of an agent that is supposed to run on a remote host, we can launch it inside the container. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512493937-23434-132 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] I supposed Grid could be the solution we're looking for, if it has some kind of an agent that is supposed to run on a remote host, we can launch it inside the container.</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512493937-23434-132--

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512493274-10340-158 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D35= 460#comment-35460 ]=20 Greg Sheremeta commented on OVIRT-1788: --------------------------------------- Take a look at the patch I linked to. # browser binaries and drivers # TODO the suite should install these and latest geckodriver FIREFOX_52_BIN =3D '/opt/firefox-52.5.0esr/firefox' FIREFOX_54_BIN =3D '/opt/firefox-54.0.1/firefox' FIREFOX_57_BIN =3D '/opt/firefox-57.0.1/firefox' It's 3 lines of python that run from an OST test: binary =3D FirefoxBinary(FIREFOX_57_BIN) os.environ['MOZ_HEADLESS'] =3D '1' driver =3D webdriver.Firefox(firefox_binary=3Dbinary) using other FF versions is simply: binary =3D FirefoxBinary(FIREFOX_56_BIN) binary =3D FirefoxBinary(FIREFOX_55_BIN) etc The python selenium library launches Firefox, and yes it can take options i= n the Firefox() constructor, but I'm not sure what you want to customize. (= The part I didn't elaborate on is Marionette, https://developer.mozilla.org= /en-US/docs/Mozilla/QA/Marionette) So, IIUC, you want to have OST running on a machine, and then Firefox in a = container and OST driving the Firefox through the container boundary? If so= , ok, that's more complex than I was aiming for. I was going to have it all= be local. I think what you want is Selenium Grid: http://www.seleniumhq.org/docs/07_s= elenium_grid.jsp """ Selenium-Grid allows you run your tests on different machines against diffe= rent browsers in parallel. That is, running multiple tests at the same time= against different machines running different browsers and operating system= s. Essentially, Selenium-Grid support distributed test execution. It allows= for running your tests in a distributed test execution environment. When to Use It Generally speaking, there=E2=80=99s two reasons why you might want to use S= elenium-Grid. To run your tests against multiple browsers, multiple versions of browser, = and browsers running on different operating systems. """ So maybe we just stand up a grid somewhere? (I believe QE has one -- [~ncre= di]? Also she knows much more about Grid than me -- I've never used it.) The grid would need to be able to connect back to the OST engine. > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chr= omium > -------------------------------------------------------------------------= ----- > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open he= adless firefox and actually open the UI, perform a login, make sure things = look good, make sure there are no ui.log errors, etc. I'll also eventually = add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test m= achine, along with chromium. There are also some binary components required= , geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, = /opt/chromium62, etc. on the machine running the suite. So I think it makes= sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we wa= nt to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512493274-10340-158 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D35460#comment-35460 ]</pre> <h3>Greg Sheremeta commented on OVIRT-1788:</h3> <p>Take a look at the patch I linked to.</p> <p># browser binaries and drivers # TODO the suite should install these and= latest geckodriver FIREFOX_52_BIN =3D ‘/opt/firefox-52.5.0esr/firefo= x’ FIREFOX_54_BIN =3D ‘/opt/firefox-54.0.1/firefox’ FIREF= OX_57_BIN =3D ‘/opt/firefox-57.0.1/firefox’</p> <p>It's 3 lines of python that run from an OST test:</p> <pre>binary =3D FirefoxBinary(FIREFOX_57_BIN) os.environ['MOZ_HEADLESS'] =3D '1' driver =3D webdriver.Firefox(firefox_binary=3Dbinary)</pre> <p>using other FF versions is simply:</p> <pre>binary =3D FirefoxBinary(FIREFOX_56_BIN) binary =3D FirefoxBinary(FIREFOX_55_BIN)</pre> <p>etc</p> <p>The python selenium library launches Firefox, and yes it can take option= s in the Firefox() constructor, but I'm not sure what you want to customize= . (The part I didn't elaborate on is Marionette, <a href=3D"https://develop= er.mozilla.org/en-US/docs/Mozilla/QA/Marionette">https://developer.mozilla.= org/en-US/docs/Mozilla/QA/Marionette</a>)</p> <p>So, IIUC, you want to have OST running on a machine, and then Firefox in= a container and OST driving the Firefox through the container boundary? If= so, ok, that's more complex than I was aiming for. I was going to have it = all be local.</p> <p>I think what you want is Selenium Grid: <a href=3D"http://www.seleniumhq= .org/docs/07_selenium_grid.jsp">http://www.seleniumhq.org/docs/07_selenium_= grid.jsp</a> """ Selenium-Grid allows you run your tests on = different machines against different browsers in parallel. That is, running= multiple tests at the same time against different machines running differe= nt browsers and operating systems. Essentially, Selenium-Grid support distr= ibuted test execution. It allows for running your tests in a distributed te= st execution environment. When to Use It Generally speaking, there=E2=80=99= s two reasons why you might want to use Selenium-Grid. To run your tests ag= ainst multiple browsers, multiple versions of browser, and browsers running= on different operating systems. """</p> <p>So maybe we just stand up a grid somewhere? (I believe QE has one &mdash= ; [~ncredi]? Also she knows much more about Grid than me — I've never= used it.)</p> <p>The grid would need to be able to connect back to the OST engine.</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multipl= e firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open h= eadless firefox and actually open the UI, perform a login, make sure things= look good, make sure there are no ui.log errors, etc. I'll also eventually= add chromium, which can run headless now too. The suite requires several f= irefox versions to be installed on the test machine, along with chromium. T= here are also some binary components required, geckodriver and chromedriver= . These are not packaged. Ideally the browsers can be installed to /opt/fir= efox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the su= ite. So I think it makes sense to maintain a custom rpm with all of this. W= here can this rpm live? What is a reliable way to do this? (I know we want = to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#1000= 74)</p> <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BJ33BSM3tuiUfRTk64K-2BOjH-2Brod5IlW2oCW2L6mmZR4CqZP8-2Fo2mgksV-2FYoRa= 1KKSyaHxiHy7u3Ic70psYh3BcrXZiTitLSss6vjRIvZwRnqzcsUnXl2fYBC8D1FsJhhv3USWqic= 26zvbCvDpaDvm9ZfemGyKMMj-2BDJGgZiQz8vAtILAMzDYXLjHVtommuM2vR0HI3tBpOte0Q3io= 05wdjHX7kdD59QCxDKDXAqdD2Z92K04-2FFV-2BPii8PI7966duV64idBwVNxBdr-2BkidHtezu= yVFdMKAloxpeEXrvZbxg-2B0BSK4SZM5slh3piExZHyEJ2MN-2F8bgZRGLOS9SvoUlUZPNyUQ9P= t9apHEhhkwrBm51StmnEVB153x0Z9oOOHM7SrVrK9u1gjblV11mfQtARbJoZHYrao6oi1kAC7Kt= COsk" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:1px !i= mportant;width:1px !important;border-width:0 !important;margin-top:0 !impor= tant;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !im= portant;padding-top:0 !important;padding-bottom:0 !important;padding-right:= 0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512493274-10340-158--

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512492584-32606-185 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- Well, can the command it uses to launch firefox be customized? We need to somehow figure out how it talks to firefox once it launches it. Can you elaborate a bit about that '(roughly)' part? How did you intend to make it work with different browser versions if they were installed in '{{/opt}}' ? > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512492584-32606-185 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>Well, can the command it uses to launch firefox be customized? We need to somehow figure out how it talks to firefox once it launches it.</p> <p>Can you elaborate a bit about that ‘(roughly)’ part?</p> <p>How did you intend to make it work with different browser versions if they were installed in ‘{{/opt}}’ ?</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512492584-32606-185--

1 0

[CQ]: 85031,2 (vdsm) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

Change 85031,2 (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/85031/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4295/

1 0

[CQ]: 85070,3 (ovirt-engine) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

Change 85070,3 (ovirt-engine) 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/85070/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4291/

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Greg Sheremeta (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512491525-30467-260 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1788: --------------------------------------- Well that's where you lose me with the container. https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008… line 55 It uses python2-selenium from OST/nose, which connects to "geckodriver", which (roughly) connects to a locally-installed Firefox. The Firefox then opens an arbitrary URL. In our case, that's URL = 'https://192.168.201.4/ovirt-engine/webadmin' USERNAME = 'admin' PASSWORD = '123' > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512491525-30467-260 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Greg Sheremeta commented on OVIRT-1788:</h3> <p>Well that's where you lose me with the container.</p> <p><a href="https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008…">https://gerrit.ovirt.org/#/c/67166/12/basic-suite-master/test-scenarios/008…</a> line 55</p> <p>It uses python2-selenium from OST/nose, which connects to “geckodriver”, which (roughly) connects to a locally-installed Firefox. The Firefox then opens an arbitrary URL. In our case, that's URL = '<a href="https://192.168.201.4/ovirt-engine/webadmin">https://192.168.201.4/ovirt-engine/webadmin</a>' USERNAME = ‘admin’ PASSWORD = ‘123’</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512491525-30467-260--

1 0

[JIRA] (OVIRT-1788) new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium
by Barak Korren (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512491211-28701-144 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1788: ------------------------------------- [~gshereme(a)redhat.com] I can make the 1st one for you, making a CentOS container with firefox installed in it is easy enough, the real challenge for me would be how to make it run headless and talk to the testing framework and oVirt. What testing framework do you intend to use? How does it communicate with the browsers it uses for testing? Does it has built-in support to the situation where the browsers are running on different containers or hosts then the testing framework (Processes in different containers typically look to one another as if they are on different hosts)? > new ui_sanity scenario for basic_suite -- need multiple firefoxes and chromium > ------------------------------------------------------------------------------ > > Key: OVIRT-1788 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: OST > Reporter: Greg Sheremeta > Assignee: infra > > I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. > The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. > Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. > Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512491211-28701-144 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1788?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren commented on OVIRT-1788:</h3> <p>[~gshereme(a)redhat.com] I can make the 1st one for you, making a CentOS container with firefox installed in it is easy enough, the real challenge for me would be how to make it run headless and talk to the testing framework and oVirt.</p> <p>What testing framework do you intend to use? How does it communicate with the browsers it uses for testing? Does it has built-in support to the situation where the browsers are running on different containers or hosts then the testing framework (Processes in different containers typically look to one another as if they are on different hosts)?</p> <blockquote><h3>new ui_sanity scenario for basic_suite — need multiple firefoxes and chromium</h3> <pre> Key: OVIRT-1788 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1788 Project: oVirt - virtualization made easy Issue Type: Improvement Components: OST Reporter: Greg Sheremeta Assignee: infra</pre> <p>I'm writing a suite that does headless UI testing. One goal is to open headless firefox and actually open the UI, perform a login, make sure things look good, make sure there are no ui.log errors, etc. I'll also eventually add chromium, which can run headless now too. The suite requires several firefox versions to be installed on the test machine, along with chromium. There are also some binary components required, geckodriver and chromedriver. These are not packaged. Ideally the browsers can be installed to /opt/firefox55, /opt/firefox56, /opt/chromium62, etc. on the machine running the suite. So I think it makes sense to maintain a custom rpm with all of this. Where can this rpm live? What is a reliable way to do this? (I know we want to avoid copr.)</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512491211-28701-144--

1 0

[JIRA] (OVIRT-1794) VM in PHX failed to migrate due to qemu bug
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512485902-15750-115 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1794?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1794: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > VM in PHX failed to migrate due to qemu bug > ------------------------------------------- > > Key: OVIRT-1794 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: > 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config > 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 > 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) > 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument > 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed > Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512485902-15750-115 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1794?page=com.atlassian.jira.… ]</pre> <h3>Evgheni Dereveanchin reassigned OVIRT-1794:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>VM in PHX failed to migrate due to qemu bug</h3> <pre> Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: Evgheni Dereveanchin Priority: Low</pre> <p>While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512485902-15750-115--

1 0

[JIRA] (OVIRT-1794) VM in PHX failed to migrate due to qemu bug
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

This is a multi-part message in MIME format... ------------=_1512485897-25186-247 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Evgheni Dereveanchin created OVIRT-1794: ------------------------------------------- Summary: VM in PHX failed to migrate due to qemu bug Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side: 2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074) ------------=_1512485897-25186-247 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Evgheni Dereveanchin created OVIRT-1794:</h3> <pre> Summary: VM in PHX failed to migrate due to qemu bug Key: OVIRT-1794 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1794 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low</pre> <p>While upgrading from 4.1.7 to 4.2-pre I experienced an issue with shift-n03 failing to migrate with error on receiving side:</p> <p>2017-12-05T14:24:53.090422Z qemu-kvm: warning: All CPU(s) up to maxcpus should be described in NUMA config 2017-12-05T14:29:41.430448Z qemu-kvm: Unknown combination of migration flags: 0 2017-12-05T14:29:41.431120Z qemu-kvm: error while loading state section id 3(ram) 2017-12-05T14:29:41.432665Z qemu-kvm: load of migration failed: Invalid argument 2017-12-05 14:29:42.271+0000: shutting down, reason=crashed</p> <p>Will shut down the VM to proceed with the upgrade but if this happens again we may need to investigate further</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1512485897-25186-247--

1 0

[CQ]: 85091,1 (ovirt-engine-sdk) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

Change 85091,1 (ovirt-engine-sdk) 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/85091/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4288/

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Daniel Belenky (oVirt JIRA) 05 Dec '17

05 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Daniel Belenky commented on OVIRT-1793: --------------------------------------- That's probably because I've performed cleanup in the mirrors server... I'm running the sync jobs now > PHX repo mirror inconsistent > ---------------------------- > > Key: OVIRT-1793 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > The [infra-docs_master_check-merged-el7-x86_64|http://jenkins.ovirt.org/job/infr…] job failed due to a missing RPM on the mirror that is present in the index: > 12:13:44 http://mirrors.phx.ovirt.org/repos/yum/epel-el7/base/f/fontawesome-fonts-4.…: [Errno 14] HTTP Error 404 - Not Found > We may need to fix this mirror or disable it for this job if this package is filtered out to conserve disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1793?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1793: ---------------------------------------- Issue Type: Bug (was: Task) > PHX repo mirror inconsistent > ---------------------------- > > Key: OVIRT-1793 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: infra > > The [infra-docs_master_check-merged-el7-x86_64|http://jenkins.ovirt.org/job/infr…] job failed due to a missing RPM on the mirror that is present in the index: > 12:13:44 http://mirrors.phx.ovirt.org/repos/yum/epel-el7/base/f/fontawesome-fonts-4.…: [Errno 14] HTTP Error 404 - Not Found > We may need to fix this mirror or disable it for this job if this package is filtered out to conserve disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[JIRA] (OVIRT-1793) PHX repo mirror inconsistent
by Evgheni Dereveanchin (oVirt JIRA) 05 Dec '17

05 Dec '17

Evgheni Dereveanchin created OVIRT-1793: ------------------------------------------- Summary: PHX repo mirror inconsistent Key: OVIRT-1793 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1793 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The [infra-docs_master_check-merged-el7-x86_64|http://jenkins.ovirt.org/job/infr…] job failed due to a missing RPM on the mirror that is present in the index: 12:13:44 http://mirrors.phx.ovirt.org/repos/yum/epel-el7/base/f/fontawesome-fonts-4.…: [Errno 14] HTTP Error 404 - Not Found We may need to fix this mirror or disable it for this job if this package is filtered out to conserve disk space. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100074)

1 0

[CQ]: 85067, 3 (ovirt-imageio) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 05 Dec '17

05 Dec '17

A system test invoked by the "ovirt-master" change queue including change 85067,3 (ovirt-imageio) failed. However, this change seems not to be the root cause for this failure. Change 85049,2 (ovirt-imageio) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 85049,2 (ovirt-imageio) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/85067/3 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/85049/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4285/

1 0

[CQ]: 85049,2 (ovirt-imageio) failed "ovirt-master" system tests
by oVirt Jenkins 05 Dec '17

05 Dec '17

Change 85049,2 (ovirt-imageio) 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/85049/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/4282/

1 0

Build failed in Jenkins: system-sync_mirrors-centos-updates-el7-x86_64 #1049
by jenkins＠jenkins.phx.ovirt.org 05 Dec '17

05 Dec '17

See <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> Changes: [Martin Sivak] Cleanup the job for ovirt-optimizer ------------------------------------------ Started by timer [EnvInject] - Loading node environment variables. Building remotely on mirrors.phx.ovirt.org (mirrors) in workspace <http://jenkins.ovirt.org/job/system-sync_mirrors-centos-updates-el7-x86_64/…> > git rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository > git config remote.origin.url http://gerrit.ovirt.org/jenkins.git # timeout=10 Cleaning workspace > git rev-parse --verify HEAD # timeout=10 Resetting working tree > git reset --hard # timeout=10 > git clean -fdx # timeout=10 Pruning obsolete local branches Fetching upstream changes from http://gerrit.ovirt.org/jenkins.git > git --version # timeout=10 > git fetch --tags --progress http://gerrit.ovirt.org/jenkins.git +refs/heads/*:refs/remotes/origin/* --prune > git rev-parse origin/master^{commit} # timeout=10 Checking out Revision 373040261719d00fc8e3003eccc3925a8c66fa66 (origin/master) > git config core.sparsecheckout # timeout=10 > git checkout -f 373040261719d00fc8e3003eccc3925a8c66fa66 Commit message: "Cleanup the job for ovirt-optimizer" > git rev-list ae00eeb7b903b253c435d6ed27ec074f2fb4d541 # timeout=10 [system-sync_mirrors-centos-updates-el7-x86_64] $ /bin/bash -xe /tmp/jenkins1628629916084377648.sh + jenkins/scripts/mirror_mgr.sh resync_yum_mirror centos-updates-el7 x86_64 jenkins/data/mirrors-reposync.conf Checking if mirror needs a resync Traceback (most recent call last): File "/usr/bin/reposync", line 343, in <module> main() File "/usr/bin/reposync", line 175, in main my.doRepoSetup() File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 681, in doRepoSetup return self._getRepos(thisrepo, True) File "/usr/lib/python2.7/site-packages/yum/__init__.py", line 721, in _getRepos self._repos.doSetup(thisrepo) File "/usr/lib/python2.7/site-packages/yum/repos.py", line 157, in doSetup self.retrieveAllMD() File "/usr/lib/python2.7/site-packages/yum/repos.py", line 88, in retrieveAllMD dl = repo._async and repo._commonLoadRepoXML(repo) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 1465, in _commonLoadRepoXML local = self.cachedir + '/repomd.xml' File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 774, in <lambda> cachedir = property(lambda self: self._dirGetAttr('cachedir')) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 757, in _dirGetAttr self.dirSetup() File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 735, in dirSetup self._dirSetupMkdir_p(dir) File "/usr/lib/python2.7/site-packages/yum/yumRepo.py", line 712, in _dirSetupMkdir_p raise Errors.RepoError, msg yum.Errors.RepoError: Error making cache directory: /home/jenkins/mirrors_cache/centos-updates-el7 error was: [Errno 17] File exists: '/home/jenkins/mirrors_cache/centos-updates-el7' Build step 'Execute shell' marked build as failure

1 1