- Infra - oVirt List Archives

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5061 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 01 Feb '17

01 Feb '17

------=_Part_311_1365014197.1485943397556 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5061/, Build Number: 5061, Build Status: SUCCESS ------=_Part_311_1365014197.1485943397556--

1 0

[ OST Failure Report ] [ oVirt master ] [ 31.01.2017 ] [add_secondary_storage_domains]
by Evgheni Dereveanchin 01 Feb '17

01 Feb '17

Test failed: add_secondary_storage_domains Links to suspected patches: https://gerrit.ovirt.org/71376 https://gerrit.ovirt.org/71427 https://gerrit.ovirt.org/71345 Link to Job: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/ Link to all logs: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/artif… Error snippet from log: 2017-01-31 05:54:53,862-0500 ERROR (jsonrpc/5) [storage.TaskManager.Task] (Task='ad8f48fc-de09-4c26-b052-7a036d7651ad') Unexpected error (task:871) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/vdsm/storage/task.py", line 878, in _run return fn(*args, **kargs) File "/usr/lib/python2.7/site-packages/vdsm/logUtils.py", line 52, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 2215, in getAllTasksInfo allTasksInfo = self._pool.getAllTasksInfo() File "/usr/lib/python2.7/site-packages/vdsm/storage/securable.py", line 77, in wrapper raise SecureError("Secured object is not in safe state") SecureError: Secured object is not in safe state Regards, Evgheni Dereveanchin

5 5

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #452 - SUCCESS!
by jenkins＠jenkins.phx.ovirt.org 01 Feb '17

01 Feb '17

------=_Part_307_56035437.1485941511598 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/452/, Build Number: 452, Build Status: SUCCESS ------=_Part_307_56035437.1485941511598--

1 0

Re: false CI -1
by Martin Mucha 01 Feb '17

01 Feb '17

Hi, this seems as false ci -1 http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/9180/con… M.

3 5

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5057 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Feb '17

01 Feb '17

------=_Part_301_18323014.1485900902576 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5057/, Build Number: 5057, Build Status: FAILURE ------=_Part_301_18323014.1485900902576--

1 1

oVirt infra daily report - unstable production jobs - 217
by jenkins＠jenkins.phx.ovirt.org 31 Jan '17

31 Jan '17

------=_Part_303_764736849.1485903614587 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/217//artifact/exported-a… Cheers, Jenkins ------=_Part_303_764736849.1485903614587 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 31/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-fc24-x86…">ovirt-system-tests_master_check-patch-fc24-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/">test-repo_ovirt_experimental_master</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_303_764736849.1485903614587--

1 0

[JIRA] (OVIRT-922) Add new project to standard ci from github
by Ondra Machacek (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] Ondra Machacek commented on OVIRT-922: -------------------------------------- A bit change. I will be executing the lago suite: https://gerrit.ovirt.org/#/c/70591/ Once it will be ready I will update. > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[JIRA] (OVIRT-1093) Re: Repository request
by eyal edri [Administrator] (oVirt JIRA) 31 Jan '17

31 Jan '17

eyal edri [Administrator] created OVIRT-1093: ------------------------------------------------ Summary: Re: Repository request Key: OVIRT-1093 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1093 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra On Jan 31, 2017 18:13, "Fabian Deutsch" <fdeutsch(a)redhat.com> wrote: > Hey, > > could you please create the following repository on gerrit: > > ovirt-on-kubevirt.git > > This repository can documentation, diagrams, and a demo of how ovirt > can consume KubeVirt. > > - fabian > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

Repository request
by Fabian Deutsch 31 Jan '17

31 Jan '17

Hey, could you please create the following repository on gerrit: ovirt-on-kubevirt.git This repository can documentation, diagrams, and a demo of how ovirt can consume KubeVirt. - fabian

2 1

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5040 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 Jan '17

31 Jan '17

------=_Part_267_1083107701.1485860151944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5040/, Build Number: 5040, Build Status: FAILURE ------=_Part_267_1083107701.1485860151944--

1 12

[JIRA] (OVIRT-1092) test-repo_ovirt_experimental_4.1 - chown error when publishing repo
by Barak Korren (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1092?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1092: ------------------------------------- The files under '/srv/resources/repos/ovirt/tested/4.1' were root-owned for some reason. I created the 4.1 repo manually (as opposed to letting the script do it), so perhaps I did it as root instead of 'deploy-ovirt-experimental' without notice. I can't tell from the history. In any case I chowned the files no, so if should be ok from now on. Next time please ping me on IRC immediately on OST issues instead of waiting for me to notice the ticket. Its a shame because we now have to log 16! failed OST runs as infra issues for something that takes less then a second to fix. > test-repo_ovirt_experimental_4.1 - chown error when publishing repo > ------------------------------------------------------------------- > > Key: OVIRT-1092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > test-repo_ovirt_experimental_4.1 is failing without visible errors on lago side. > Checking job logs, there's the following error when publishing RPMs: > 12:24:49 Copying to published repo > 12:24:49 + echo 'Copying to published repo' > 12:24:49 + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/4.1 > 12:24:49 install: cannot change owner and permissions of ‘/srv/resources/repos/ovirt/tested/4.1’: Operation not permitted > 12:24:49 + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock > [Pipeline] } //sshagent > [Pipeline] SSH Agent : End > [Pipeline] } //wrap > [Pipeline] General Build Wrapper : End > [Pipeline] } //node > [Pipeline] Allocate node : End > [Pipeline] End of Pipeline > ERROR: script returned exit code 1 > Finished: FAILURE > There was no "install" command in logs before builds started failing > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/436/console -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

Build failed in Jenkins: deploy-to-ovirt_experimental_master #11110
by jenkins＠jenkins.phx.ovirt.org 31 Jan '17

31 Jan '17

See <http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental_master/11110/> ------------------------------------------ [...truncated 3.64 KB...] temp_dir = generate-in-repo stores = RPMStore,IsoStore 2017-01-31 16:40:58,723::INFO::repoman.cmd.main:452:: 2017-01-31 16:40:58,724::INFO::repoman.cmd.do_add:336::Adding artifacts to the repo /srv/resources/repos/ovirt/experimental 2017-01-31 16:40:58,724::INFO::repoman.common.repo.add_source:169::Adding repo extra dir master 2017-01-31 16:40:58,724::DEBUG::repoman.common.repo.rebase:264::Rebasing repo /srv/resources/repos/ovirt/experimental to /srv/resources/repos/ovirt/experimental/master 2017-01-31 16:40:58,724::DEBUG::repoman.common.repo.__init__:71::### Defaults: [main] allowed_repo_paths = temp_dir = generate singing_key = signing_passphrase = ask stores = all filters = all sources = all verify_ssl = true on_empty_source = fail [store.RPMStore] distro_reg = \.(fc|el)\d+(?=\w*) with_srcrpms = true signing_passphrase = ask on_wrong_distro = fail path_prefix = rpm,src rpm_dir = rpm temp_dir = generate with_sources = false signing_key = extra_symlinks = [store.IsoStore] signing_passphrase = ask signing_key = temp_dir = generate path_prefix = iso [filter.OnlyMissingFilter] [filter.LatestFilter] [filter.NameFilter] [source.JenkinsSource] jenkins_host_re = jenkins\.ovirt\.org [source.KojiBuildSource] koji_extra_opts = krbservice=host koji_topurl = https://kojipkgs.fedoraproject.org/ koji_server = https://koji.fedoraproject.org/kojihub koji_skip_unavailable = true [source.URLSource] [source.KojiURLSource] koji_host_re = koji\.fedoraproject\.org [source.DirSource] allowed_dir_paths = ### Config [main] allowed_repo_paths = /srv/resources/repos/ovirt/experimental temp_dir = /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n stores = RPMStore,IsoStore 2017-01-31 16:40:58,726::INFO::repoman.common.repo.add_source:169::Adding repo extra dir ovirt-engine_fc25_485 2017-01-31 16:40:58,727::DEBUG::repoman.common.repo.rebase:264::Rebasing repo /srv/resources/repos/ovirt/experimental/master to /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 2017-01-31 16:40:58,727::DEBUG::repoman.common.repo.__init__:71::### Defaults: [main] allowed_repo_paths = temp_dir = generate singing_key = signing_passphrase = ask stores = all filters = all sources = all verify_ssl = true on_empty_source = fail [store.RPMStore] distro_reg = \.(fc|el)\d+(?=\w*) with_srcrpms = true signing_passphrase = ask on_wrong_distro = fail path_prefix = rpm,src rpm_dir = rpm temp_dir = generate with_sources = false signing_key = extra_symlinks = [store.IsoStore] signing_passphrase = ask signing_key = temp_dir = generate path_prefix = iso [filter.OnlyMissingFilter] [filter.LatestFilter] [filter.NameFilter] [source.JenkinsSource] jenkins_host_re = jenkins\.ovirt\.org [source.KojiBuildSource] koji_extra_opts = krbservice=host koji_topurl = https://kojipkgs.fedoraproject.org/ koji_server = https://koji.fedoraproject.org/kojihub koji_skip_unavailable = true [source.URLSource] [source.KojiURLSource] koji_host_re = koji\.fedoraproject\.org [source.DirSource] allowed_dir_paths = ### Config [main] allowed_repo_paths = /srv/resources/repos/ovirt/experimental temp_dir = /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n/tmpD30571 stores = RPMStore,IsoStore 2017-01-31 16:40:58,729::DEBUG::repoman.common.repo.load:103::Loading repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 2017-01-31 16:40:58,732::INFO::repoman.common.stores.RPM.__init__:164::Loading repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 2017-01-31 16:40:58,732::INFO::repoman.common.stores.RPM.__init__:171::Repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 loaded 2017-01-31 16:40:58,734::INFO::repoman.common.stores.iso.__init__:138::Loading repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 2017-01-31 16:40:58,734::INFO::repoman.common.stores.iso.__init__:145::Repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 loaded 2017-01-31 16:40:58,747::INFO::repoman.common.repo.add_source:174::Resolving artifact source http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,747::DEBUG::repoman.common.parser.parse:73::Checking source JenkinsSource with http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,748::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… is an iso 2017-01-31 16:40:58,749::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,782::INFO::requests.packages.urllib3.connectionpool._new_conn:203::Starting new HTTP connection (1): jenkins.ovirt.org 2017-01-31 16:40:58,813::DEBUG::requests.packages.urllib3.connectionpool._make_request:383::"GET /job/ovirt-engine_master_build-artifacts-fc25-x86_64/485//api/json?depth=3 HTTP/1.1" 200 3033 2017-01-31 16:40:58,820::INFO::repoman.common.sources.jenkins.expand:93::Parsing jenkins URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,820::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.build-artifacts.sh/build-artifacts.sh.log is an iso 2017-01-31 16:40:58,820::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,821::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.clean_rpmdb/stdout_stderr.log is an iso 2017-01-31 16:40:58,821::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,821::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.init/build.log is an iso 2017-01-31 16:40:58,821::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,822::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.init/root.log is an iso 2017-01-31 16:40:58,822::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,822::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.init/state.log is an iso 2017-01-31 16:40:58,823::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,823::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/mock_logs/mocker-fedora-25-x86_64.fc25.init/stdout_stderr.log is an iso 2017-01-31 16:40:58,823::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,823::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,824::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,824::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/ovirt-engine-4.2.0_master.tar.gz is an iso 2017-01-31 16:40:58,824::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,824::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,825::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,825::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,825::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,826::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,826::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,826::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,827::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,827::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,827::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,828::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,828::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,828::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,828::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,829::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,829::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,829::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,830::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,830::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,830::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,831::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,831::INFO::repoman.common.sources.jenkins.expand:108:: Got URL: http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… 2017-01-31 16:40:58,831::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/0172f07444c90ee5b6cf1effc5379bc884343f0cf70d0963201491ee43f12f63-primary.xml.gz is an iso 2017-01-31 16:40:58,831::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,832::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/0395ec5eb9c18c006741424ca5ed65145fd647cf9cde5f152215470ba811ea63-primary.sqlite.bz2 is an iso 2017-01-31 16:40:58,832::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,832::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/7f5702835e6447c25a3642897e228f1f6f8b38923227c09eb598aa0813b7aec4-filelists.sqlite.bz2 is an iso 2017-01-31 16:40:58,832::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,833::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/a0f55ab7c14acc2a5c2996f8a863ce2b0aee2209dded8c2abee290dc4c8af603-other.sqlite.bz2 is an iso 2017-01-31 16:40:58,833::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,833::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/acef171ff1312f57e78bf771691ace75fb119df1a7c61a2624d053e0ee4a0980-other.xml.gz is an iso 2017-01-31 16:40:58,833::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,834::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/f83a3e11a6304a1356d3e0dd8625e77f5369cb692b205e7ff0d77b25703cda9b-filelists.xml.gz is an iso 2017-01-31 16:40:58,834::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,834::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if exported-artifacts/repodata/repomd.xml is an iso 2017-01-31 16:40:58,834::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,835::INFO::root.expand:111:: Done 2017-01-31 16:40:58,835::DEBUG::root.parse:115::From source string http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… got: [u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…', u'http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…'] 2017-01-31 16:40:58,838::INFO::requests.packages.urllib3.connectionpool._new_conn:203::Starting new HTTP connection (1): jenkins.ovirt.org 2017-01-31 16:40:58,859::DEBUG::requests.packages.urllib3.connectionpool._make_request:383::"HEAD /job/ovirt-engine_master_build-artifacts-fc25-x86_64/485//artifact/exported-artifacts/ovirt-engine-4.2.0-0.0.master.20170131163004.git7a08505.fc25.noarch.rpm HTTP/1.1" 200 0 2017-01-31 16:40:58,861::INFO::root.download:221::Downloading http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…, length 2M ... 2017-01-31 16:40:58,864::INFO::requests.packages.urllib3.connectionpool._new_conn:203::Starting new HTTP connection (1): jenkins.ovirt.org 2017-01-31 16:40:58,880::DEBUG::requests.packages.urllib3.connectionpool._make_request:383::"GET /job/ovirt-engine_master_build-artifacts-fc25-x86_64/485//artifact/exported-artifacts/ovirt-engine-4.2.0-0.0.master.20170131163004.git7a08505.fc25.noarch.rpm HTTP/1.1" 200 2223210 %[-----------------------25------------------------50-----------------------75------------------------] %[====================================================================================================] 2017-01-31 16:40:58,953::INFO::repoman.common.stores.RPM.add_rpm:248::Adding package /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n/tmpD30571/tmpTiVgOJ/ovirt-engine-4.2.0-0.0.master.20170131163004.git7a08505.fc25.noarch.rpm to repo /srv/resources/repos/ovirt/experimental/master/ovirt-engine_fc25_485 2017-01-31 16:40:58,953::DEBUG::repoman.common.stores.iso.handles_artifact:152::Checking if http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… is an iso 2017-01-31 16:40:58,953::DEBUG::repoman.common.stores.iso.handles_artifact:158:: It is not 2017-01-31 16:40:58,956::INFO::requests.packages.urllib3.connectionpool._new_conn:203::Starting new HTTP connection (1): jenkins.ovirt.org 2017-01-31 16:40:58,977::DEBUG::requests.packages.urllib3.connectionpool._make_request:383::"HEAD /job/ovirt-engine_master_build-artifacts-fc25-x86_64/485//artifact/exported-artifacts/ovirt-engine-4.2.0-0.0.master.20170131163004.git7a08505.fc25.src.rpm HTTP/1.1" 200 0 2017-01-31 16:40:58,979::INFO::root.download:221::Downloading http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6…, length 9M ... 2017-01-31 16:40:58,982::INFO::requests.packages.urllib3.connectionpool._new_conn:203::Starting new HTTP connection (1): jenkins.ovirt.org Traceback (most recent call last): File "/usr/bin/repoman", line 10, in <module> sys.exit(main()) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 455, in main exit_code = do_add(args, config, repo) File "/usr/lib/python2.7/site-packages/repoman/cmd.py", line 338, in do_add repo.add_source(art_src.strip()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 153, in add_source self.parse_source_stream(sys.stdin.readlines()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 193, in parse_source_stream self.add_source(line.strip()) File "/usr/lib/python2.7/site-packages/repoman/common/repo.py", line 179, in add_source store.add_artifact(artifact_path) File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py", line 192, in add_artifact self.add_rpm(pkg, **args) File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/__init__.py", line 213, in add_rpm verify_ssl=self.config.getboolean('verify_ssl'), File "/usr/lib/python2.7/site-packages/repoman/common/stores/RPM/RPM.py", line 109, in __init__ download(path, fpath, verify=verify_ssl) File "/usr/lib/python2.7/site-packages/repoman/common/utils.py", line 224, in download stream = requests.get(path, stream=True, verify=verify) File "/usr/lib/python2.7/site-packages/requests/api.py", line 68, in get return request('get', url, **kwargs) File "/usr/lib/python2.7/site-packages/requests/api.py", line 50, in request response = session.request(method=method, url=url, **kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 464, in request resp = self.send(prep, **send_kwargs) File "/usr/lib/python2.7/site-packages/requests/sessions.py", line 576, in send r = adapter.send(request, **kwargs) File "/usr/lib/python2.7/site-packages/requests/adapters.py", line 415, in send raise ConnectionError(err, request=request) requests.exceptions.ConnectionError: ('Connection aborted.', gaierror(-2, 'Name or service not known')) 2017-01-31 16:41:19,411::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n/tmpD30571/tmpTiVgOJ 2017-01-31 16:41:19,412::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n/tmpD30571 2017-01-31 16:41:19,412::INFO::repoman.common.repo.cleanup:35::Cleaning up temporary dir /srv/resources/repos/ovirt/experimental/.lago_tmp/tmpBm5x4n + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock Build step 'Execute shell' marked build as failure [ssh-agent] Stopped.

1 1

[JIRA] (OVIRT-1092) test-repo_ovirt_experimental_4.1 - chown error when publishing repo
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1092?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1092: --------------------------------------------- Here's the patch that added "install": https://gerrit.ovirt.org/71137 [~bkorren(a)redhat.com] could you please check why it fails on test-repo_ovirt_experimental_4.1? Works fine with master - maybe some permissions or ownership has to be changed. > test-repo_ovirt_experimental_4.1 - chown error when publishing repo > ------------------------------------------------------------------- > > Key: OVIRT-1092 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1092 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Evgheni Dereveanchin > Assignee: infra > Priority: High > > test-repo_ovirt_experimental_4.1 is failing without visible errors on lago side. > Checking job logs, there's the following error when publishing RPMs: > 12:24:49 Copying to published repo > 12:24:49 + echo 'Copying to published repo' > 12:24:49 + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/4.1 > 12:24:49 install: cannot change owner and permissions of ‘/srv/resources/repos/ovirt/tested/4.1’: Operation not permitted > 12:24:49 + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock > [Pipeline] } //sshagent > [Pipeline] SSH Agent : End > [Pipeline] } //wrap > [Pipeline] General Build Wrapper : End > [Pipeline] } //node > [Pipeline] Allocate node : End > [Pipeline] End of Pipeline > ERROR: script returned exit code 1 > Finished: FAILURE > There was no "install" command in logs before builds started failing > http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/436/console -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[JIRA] (OVIRT-1092) test-repo_ovirt_experimental_4.1 - chown error when publishing repo
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '17

31 Jan '17

Evgheni Dereveanchin created OVIRT-1092: ------------------------------------------- Summary: test-repo_ovirt_experimental_4.1 - chown error when publishing repo Key: OVIRT-1092 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1092 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Evgheni Dereveanchin Assignee: infra Priority: High test-repo_ovirt_experimental_4.1 is failing without visible errors on lago side. Checking job logs, there's the following error when publishing RPMs: 12:24:49 Copying to published repo 12:24:49 + echo 'Copying to published repo' 12:24:49 + install -o deploy-ovirt-experimental -m 755 -d /srv/resources/repos/ovirt/tested/4.1 12:24:49 install: cannot change owner and permissions of ‘/srv/resources/repos/ovirt/tested/4.1’: Operation not permitted 12:24:49 + rm -f /home/deploy-ovirt-experimental/experimental_repo.lock [Pipeline] } //sshagent [Pipeline] SSH Agent : End [Pipeline] } //wrap [Pipeline] General Build Wrapper : End [Pipeline] } //node [Pipeline] Allocate node : End [Pipeline] End of Pipeline ERROR: script returned exit code 1 Finished: FAILURE There was no "install" command in logs before builds started failing http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/436/console -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

Recent DNS problems affecting oVirt
by Marc Dequènes (Duck) 31 Jan '17

31 Jan '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --huopoviSJIeJd1aoc6shTPlqH6gIDlvq5 Content-Type: multipart/mixed; boundary="Kl6xjSCgbAD7kKv3wNlWk5ROmFD0lliMu"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <1a019dcf-1407-76b2-523a-8492f2f8c3cd(a)redhat.com> Subject: Recent DNS problems affecting oVirt --Kl6xjSCgbAD7kKv3wNlWk5ROmFD0lliMu Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, OSAS is acting NS2/MX2 for oVirt (for phx.ovirt.org only for DNS). A few days ago I found out a few mails (less than ten at this time) rejected on the MX for the oVirt MLs. It was like the DNS resolvers were cracking nuts, and Postfix rejected mail due to the ovirt.org domain not existing.= I reported this problem with preliminary debug while flying to DevConf.cz, disabling MX2 to avoid more rejections, and Misc with IT found out the problem: IT had decommissioned a DNS server but the glue records where wrong. Unfortunately the old DNS server was still working but giving bad results, so this caused some disruption in the force. It is solved and there is no more problems in this area. \_o< --Kl6xjSCgbAD7kKv3wNlWk5ROmFD0lliMu-- --huopoviSJIeJd1aoc6shTPlqH6gIDlvq5 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAliQfWYACgkQVen596wc RD9DRw/+ON9iGFzpGbVIpG1uQqCOP9cjYFFYpeJpfAjK4lxLcJmC3m3mPbOphBIn tcPY3mqUqYLIq0sZPDCRPBN8xPU4e9eE58+RX275bd+fUytOCgg6qBQTGqKLK7KX ZY2A78UiNglvW6bTyZTmG4fLG4Go3yJrG4Lm6L9PCYkq6e2Oy+mlRonv/gRA9PQZ oWY1AOh5ioM5UvTGWJYJyklgvmG0qg5a0kNMdsREUCaoOKFJMyF3HPxGTGKBbmU6 9iKKBcpFKQdSpjslXZN99oP56Az2IZTDGrLzDGsd8Rog1eXBv0NCSwON2Qd7a0Ds oSasHWLyHsIsIu0YIVDlaIGjxeVhBYTCoJbJKvTxD/EHjKG5PA/BwGefQljwW9V7 eyIe+sQcAQx/8o5+RcksBXQiCTYg/Z6oxnqMYCwbyTchG1v5JvJzNgsf2PzbXVj/ 0NXw8XUW2dld1kg9OsrtqS4uQ5IZTWnGZEp2yQt9Z9crXIYJjJPEoZLvoTh2djKN +8tTihq9cRCS5vJUqI2tqNsiELBdgVou+wqshJ698e4wOJI5bvRUMQS39eSrAYXa k9V3Ga7mqNSgBc/iY/T8f4Ppo4Hbn+fx9YKuTyYzRVaB0F2qCnDvF9fGWmlHO55U tXVzMmMKzb68B2fbKHzutqGNgrY5zKabFpbidWdEUuvWs+13h34= =hqwH -----END PGP SIGNATURE----- --huopoviSJIeJd1aoc6shTPlqH6gIDlvq5--

1 0

[JIRA] (OVIRT-1091) Add yum repo "awareness" to repoman
by Barak Korren (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1091?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1091: ----------------------------------- Assignee: Anton Marchukov (was: infra) > Add yum repo "awareness" to repoman > ----------------------------------- > > Key: OVIRT-1091 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1091 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: Anton Marchukov > > {{repoman}} currently has no support for {{yum}} repos at all. When it gets a URL as a package source, {{repoman}} currently first attempts to detect if that URL is a Jenkins job, and if not, it just tries to download the artefact directly from the URL. To use a {{yum}} repo with {{repoman}}, one need to explicitly specify the '{{rec:}}' flag, to make it search for artifacts recursively. > Full {{yum}} support in {{repoman}} can have many features, such as reading the {{yum}} metadata files to figure out which packages are in the repo, and preforming version calculations prior to downloading packages. This ticket is not about that. > This ticket suggests a simpler implementation to make {{repoman}} "aware" of {{yum}} repos to make it slightly easier to use and reduce user surprise while full {{yum}} support is being developed. > It is suggested that when receiving a source URL, {{repoman}} will check for a '{{*/repodata/repomd.xml}}' file in a similar fashion to the way it checks for the Jenkins API, and if found will act as if the '{{rec:}}' flag was specified. -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[JIRA] (OVIRT-1091) Add yum repo "awareness" to repoman
by Barak Korren (oVirt JIRA) 31 Jan '17

31 Jan '17

Barak Korren created OVIRT-1091: ----------------------------------- Summary: Add yum repo "awareness" to repoman Key: OVIRT-1091 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1091 Project: oVirt - virtualization made easy Issue Type: Improvement Components: repoman Reporter: Barak Korren Assignee: infra {{repoman}} currently has no support for {{yum}} repos at all. When it gets a URL as a package source, {{repoman}} currently first attempts to detect if that URL is a Jenkins job, and if not, it just tries to download the artefact directly from the URL. To use a {{yum}} repo with {{repoman}}, one need to explicitly specify the '{{rec:}}' flag, to make it search for artifacts recursively. Full {{yum}} support in {{repoman}} can have many features, such as reading the {{yum}} metadata files to figure out which packages are in the repo, and preforming version calculations prior to downloading packages. This ticket is not about that. This ticket suggests a simpler implementation to make {{repoman}} "aware" of {{yum}} repos to make it slightly easier to use and reduce user surprise while full {{yum}} support is being developed. It is suggested that when receiving a source URL, {{repoman}} will check for a '{{*/repodata/repomd.xml}}' file in a similar fashion to the way it checks for the Jenkins API, and if found will act as if the '{{rec:}}' flag was specified. -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[JIRA] (OVIRT-1091) Add yum repo "awareness" to repoman
by Barak Korren (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1091?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1091: -------------------------------- Epic Link: OVIRT-403 > Add yum repo "awareness" to repoman > ----------------------------------- > > Key: OVIRT-1091 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1091 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: repoman > Reporter: Barak Korren > Assignee: infra > > {{repoman}} currently has no support for {{yum}} repos at all. When it gets a URL as a package source, {{repoman}} currently first attempts to detect if that URL is a Jenkins job, and if not, it just tries to download the artefact directly from the URL. To use a {{yum}} repo with {{repoman}}, one need to explicitly specify the '{{rec:}}' flag, to make it search for artifacts recursively. > Full {{yum}} support in {{repoman}} can have many features, such as reading the {{yum}} metadata files to figure out which packages are in the repo, and preforming version calculations prior to downloading packages. This ticket is not about that. > This ticket suggests a simpler implementation to make {{repoman}} "aware" of {{yum}} repos to make it slightly easier to use and reduce user surprise while full {{yum}} support is being developed. > It is suggested that when receiving a source URL, {{repoman}} will check for a '{{*/repodata/repomd.xml}}' file in a similar fashion to the way it checks for the Jenkins API, and if found will act as if the '{{rec:}}' flag was specified. -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[JIRA] (OVIRT-1088) Block internet access to mirrors.phx.ovirt.org
by Evgheni Dereveanchin (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1088?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1088: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Block internet access to mirrors.phx.ovirt.org > ---------------------------------------------- > > Key: OVIRT-1088 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1088 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > > mirrors.phx.ovirt.org currently allows HTTP access from the entire internet. It was convenient while it was being deployed, but now it should be changed to allow access only from the PHC data center. -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5035 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 31 Jan '17

31 Jan '17

------=_Part_251_950026046.1485850244528 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5035/, Build Number: 5035, Build Status: FAILURE ------=_Part_251_950026046.1485850244528--

1 2

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by eyal edri [Administrator] (oVirt JIRA) 31 Jan '17

31 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1090?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1090: --------------------------------------------- Resolution: Fixed Status: Done (was: To Do) > [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras > ------------------------------------------------------------------------------ > > Key: OVIRT-1090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We're one week after initial report that vdsm is missing in fc24 repository > for master. > We have automation broken due to this. > Please restore vdsm builder for fc24 master, it's affecting CI for > hosted-engine, ovirt-release, and possibly other projects... > On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > > >> VDSM master fc24 is not supported. > > > > > > This is the only fedora version we support now. > > > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > > > It's a one-liner configuration change to have Vdsm use the > > python-native SSL support. > > We should not drag f24 just for that; we'd better just modify the > > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.4#100026)

1 0

oVirt infra daily report - unstable production jobs - 216
by jenkins＠jenkins.phx.ovirt.org 30 Jan '17

30 Jan '17

------=_Part_249_1810811421.1485817206367 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/216//artifact/exported-a… Cheers, Jenkins ------=_Part_249_1810811421.1485817206367 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 30/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_249_1810811421.1485817206367--

1 0

Re: ** PROBLEM Service Alert: ovirt-mirrorchecker/mirrors.ibiblio.org/ovirt/pub mirror site last sync is CRITICAL **
by Nadav Goldin 30 Jan '17

30 Jan '17

Looks good! Thanks, Nadav. On Mon, Jan 30, 2017 at 9:13 PM, Don Sizemore <dls(a)ibiblio.org> wrote: > Hello, > > An rsync run from Jan 18 was still sitting there. I've just now kicked and > restarted it. > > Thank you, > Donald > > > thank you, > don sizemore, ii > 919.260.4915 (c) > > On Mon, Jan 30, 2017 at 1:56 PM, Nadav Goldin <ngoldin(a)redhat.com> wrote: >> >> Hi again, >> The oVirt mirror site at ibiblio.org seems to be out of sync for more >> than 12 days, >> >> could you please take a look? >> >> Thanks, >> >> Nadav. >> >> >> ---------- Forwarded message ---------- >> From: icinga <icinga(a)monitoring.ovirt.org> >> Date: Mon, Jan 30, 2017 at 8:39 PM >> Subject: ** PROBLEM Service Alert: >> ovirt-mirrorchecker/mirrors.ibiblio.org/ovirt/pub mirror site last >> sync is CRITICAL ** >> To: ngoldin(a)redhat.com >> >> >> ***** Icinga ***** >> >> Notification Type: PROBLEM >> >> Service: mirrors.ibiblio.org/ovirt/pub mirror site last sync >> Host: ovirt-mirrorchecker >> Address: 66.187.230.105 >> State: CRITICAL >> >> Date/Time: Mon Jan 30 18:39:53 UTC 2017 >> >> Additional Info: >> >> CRITICAL - 1073940 seconds since last sync, which are 298.3167 hours. > >

1 0

Fwd: ** PROBLEM Service Alert: ovirt-mirrorchecker/mirrors.ibiblio.org/ovirt/pub mirror site last sync is CRITICAL **
by Nadav Goldin 30 Jan '17

30 Jan '17

Hi again, The oVirt mirror site at ibiblio.org seems to be out of sync for more than 12 days, could you please take a look? Thanks, Nadav. ---------- Forwarded message ---------- From: icinga <icinga(a)monitoring.ovirt.org> Date: Mon, Jan 30, 2017 at 8:39 PM Subject: ** PROBLEM Service Alert: ovirt-mirrorchecker/mirrors.ibiblio.org/ovirt/pub mirror site last sync is CRITICAL ** To: ngoldin(a)redhat.com ***** Icinga ***** Notification Type: PROBLEM Service: mirrors.ibiblio.org/ovirt/pub mirror site last sync Host: ovirt-mirrorchecker Address: 66.187.230.105 State: CRITICAL Date/Time: Mon Jan 30 18:39:53 UTC 2017 Additional Info: CRITICAL - 1073940 seconds since last sync, which are 298.3167 hours.

1 0

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1090?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1090: -------------------------------------------------- restored the previous configuration in [1], new job available [2]. If this needs to change, vdsm maintainers can send a new patch. [1] https://gerrit.ovirt.org/#/c/71401/1 [2] http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/7/cons… > [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras > ------------------------------------------------------------------------------ > > Key: OVIRT-1090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We're one week after initial report that vdsm is missing in fc24 repository > for master. > We have automation broken due to this. > Please restore vdsm builder for fc24 master, it's affecting CI for > hosted-engine, ovirt-release, and possibly other projects... > On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > > >> VDSM master fc24 is not supported. > > > > > > This is the only fedora version we support now. > > > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > > > It's a one-liner configuration change to have Vdsm use the > > python-native SSL support. > > We should not drag f24 just for that; we'd better just modify the > > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1090?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1090: -------------------------------------------------- Which was approved by vdsm maintainers. And still the question remains on which fedora version should be supported, fc24 or fc25 which didn't got a final answer by the maintainers. On Jan 30, 2017 7:11 PM, "sbonazzo (oVirt JIRA)" < > [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras > ------------------------------------------------------------------------------ > > Key: OVIRT-1090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We're one week after initial report that vdsm is missing in fc24 repository > for master. > We have automation broken due to this. > Please restore vdsm builder for fc24 master, it's affecting CI for > hosted-engine, ovirt-release, and possibly other projects... > On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > > >> VDSM master fc24 is not supported. > > > > > > This is the only fedora version we support now. > > > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > > > It's a one-liner configuration change to have Vdsm use the > > python-native SSL support. > > We should not drag f24 just for that; we'd better just modify the > > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by sbonazzo (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1090?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-1090: --------------------------------- It's an infra related issue being fedora 24 removed from nightly publisher by infra: commit 029a68ee63ffda8220d8570b09a7de60cc08eb1d Author: Eyal Edri <eedri(a)redhat.com> Date: Wed Dec 28 13:27:59 2016 +0200 Refactoring vdsm yaml 1.Keep all excludes in the commons to avoid errors and missing or unneeded permutations 2.Removing fc24 publishing for master nightly snapshots should be replaced by fc25 gradually by project owners. Change-Id: I29f6534f0dfa186106bd68c94e72a87a1325158f Signed-off-by: Eyal Edri <eedri(a)redhat.com> -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com > [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras > ------------------------------------------------------------------------------ > > Key: OVIRT-1090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We're one week after initial report that vdsm is missing in fc24 repository > for master. > We have automation broken due to this. > Please restore vdsm builder for fc24 master, it's affecting CI for > hosted-engine, ovirt-release, and possibly other projects... > On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > > >> VDSM master fc24 is not supported. > > > > > > This is the only fedora version we support now. > > > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > > > It's a one-liner configuration change to have Vdsm use the > > python-native SSL support. > > We should not drag f24 just for that; we'd better just modify the > > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

2 1

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by sbonazzo (oVirt JIRA) 30 Jan '17

30 Jan '17

sbonazzo created OVIRT-1090: ------------------------------- Summary: [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras Key: OVIRT-1090 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: sbonazzo Assignee: infra We're one week after initial report that vdsm is missing in fc24 repository for master. We have automation broken due to this. Please restore vdsm builder for fc24 master, it's affecting CI for hosted-engine, ovirt-release, and possibly other projects... On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > >> VDSM master fc24 is not supported. > > > > This is the only fedora version we support now. > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > It's a one-liner configuration change to have Vdsm use the > python-native SSL support. > We should not drag f24 just for that; we'd better just modify the > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > _______________________________________________ > Devel mailing list > Devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/devel > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

3 2

[JIRA] (OVIRT-1090) [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1090?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1090: -------------------------------------------------- How is this an infra issue? If vdsm maintainers don't think fedora builds are a priority for master and not working towards restoring it, then I guess we need to drop fedora support for master until this decision is made. I saw mixed thoughts on the devel list on what should be supported or built for master, so until we have a final decision from maintainers, no sure what action item we can do here. On Jan 30, 2017 6:50 PM, "sbonazzo (oVirt JIRA)" < > [URGENT][ACTION REQUIRED] Re: [ovirt-devel] Missing vdsm snapshots for Fedoras > ------------------------------------------------------------------------------ > > Key: OVIRT-1090 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1090 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > We're one week after initial report that vdsm is missing in fc24 repository > for master. > We have automation broken due to this. > Please restore vdsm builder for fc24 master, it's affecting CI for > hosted-engine, ovirt-release, and possibly other projects... > On Thu, Jan 26, 2017 at 2:54 PM, Dan Kenigsberg <danken(a)redhat.com> wrote: > > On Thu, Jan 26, 2017 at 11:23 AM, Nir Soffer <nsoffer(a)redhat.com> wrote: > > > On Thu, Jan 26, 2017 at 11:17 AM, Gil Shinar <gshinar(a)redhat.com> wrote: > > >> VDSM master fc24 is not supported. > > > > > > This is the only fedora version we support now. > > > > > > Vdsm on Fedora 25 is broken due to m2crypto changes. > > > > It's a one-liner configuration change to have Vdsm use the > > python-native SSL support. > > We should not drag f24 just for that; we'd better just modify the > > default for Fedora 25 a-la https://gerrit.ovirt.org/#/c/71248/ > > _______________________________________________ > > Devel mailing list > > Devel(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/devel > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #5020 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Jan '17

30 Jan '17

------=_Part_227_976981314.1485786057926 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/5020/, Build Number: 5020, Build Status: FAILURE ------=_Part_227_976981314.1485786057926--

1 1

[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
by Tal Nisan (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-1089: ---------------------------------- I will, I'm dedicated to make my life as a stable branch maintainer easier, thanks for that ;) On Mon, Jan 30, 2017 at 3:34 PM, Eyal Edri <eedri(a)redhat.com> wrote: > +1, thanks. > > Please continue to let us know if we need to enforce other hooks more > strictly as well :) > > On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > >> Yeah I've noticed the hook identified the situation, I'm asking you to >> make it more stricter, hence the email :) >> >> On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri <eedri(a)redhat.com> wrote: >> >>> It already WARN on it: >>> >>> - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >>> >>> We can make it more strict and give VERIFY -1. >>> Adding infra-support to open a ticket on it. >>> >>> We intentionally didn't enforce Verify as default since we wanted to >>> give time to the hook >>> to work and see we don't have false positives on it. >>> >>> >>> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: >>> >>>> Example: >>>> https://gerrit.ovirt.org/#/c/71374/ >>>> >>>> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >>>> pushed into the 4.1 stable branch >>>> >>>> Thanks. >>>> >>>> _______________________________________________ >>>> Infra mailing list >>>> Infra(a)ovirt.org >>>> http://lists.ovirt.org/mailman/listinfo/infra >>>> >>>> >>> >>> >>> -- >>> Eyal Edri >>> Associate Manager >>> RHV DevOps >>> EMEA ENG Virtualization R&D >>> Red Hat Israel >>> >>> phone: +972-9-7692018 <+972%209-769-2018> >>> irc: eedri (on #tlv #rhev-dev #rhev-integ) >>> >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > Re: Wrong target milestone bugs should be blocked with -verified on the stable branches > --------------------------------------------------------------------------------------- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > It already WARN on it: > - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

Wrong target milestone bugs should be blocked with -verified on the stable branches
by Tal Nisan 30 Jan '17

30 Jan '17

Example: https://gerrit.ovirt.org/#/c/71374/ I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is pushed into the 4.1 stable branch Thanks.

2 4

[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1089: -------------------------------------------------- +1, thanks. Please continue to let us know if we need to enforce other hooks more strictly as well :) On Mon, Jan 30, 2017 at 3:29 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > Yeah I've noticed the hook identified the situation, I'm asking you to > make it more stricter, hence the email :) > > On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri <eedri(a)redhat.com> wrote: > >> It already WARN on it: >> >> - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 >> >> We can make it more strict and give VERIFY -1. >> Adding infra-support to open a ticket on it. >> >> We intentionally didn't enforce Verify as default since we wanted to give >> time to the hook >> to work and see we don't have false positives on it. >> >> >> On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: >> >>> Example: >>> https://gerrit.ovirt.org/#/c/71374/ >>> >>> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >>> pushed into the 4.1 stable branch >>> >>> Thanks. >>> >>> _______________________________________________ >>> Infra mailing list >>> Infra(a)ovirt.org >>> http://lists.ovirt.org/mailman/listinfo/infra >>> >>> >> >> >> -- >> Eyal Edri >> Associate Manager >> RHV DevOps >> EMEA ENG Virtualization R&D >> Red Hat Israel >> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) > Re: Wrong target milestone bugs should be blocked with -verified on the stable branches > --------------------------------------------------------------------------------------- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > It already WARN on it: > - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
by Tal Nisan (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-1089: ---------------------------------- Yeah I've noticed the hook identified the situation, I'm asking you to make it more stricter, hence the email :) On Mon, Jan 30, 2017 at 3:22 PM, Eyal Edri <eedri(a)redhat.com> wrote: > It already WARN on it: > > - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > > > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > >> Example: >> https://gerrit.ovirt.org/#/c/71374/ >> >> I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is >> pushed into the 4.1 stable branch >> >> Thanks. >> >> _______________________________________________ >> Infra mailing list >> Infra(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/infra >> >> > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > > phone: +972-9-7692018 <+972%209-769-2018> > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > Re: Wrong target milestone bugs should be blocked with -verified on the stable branches > --------------------------------------------------------------------------------------- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > It already WARN on it: > - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1089?page=com.atlassian.jira.… ] eyal edri [Administrator] reassigned OVIRT-1089: ------------------------------------------------ Assignee: Shlomo Ben David (was: infra) > Re: Wrong target milestone bugs should be blocked with -verified on the stable branches > --------------------------------------------------------------------------------------- > > Key: OVIRT-1089 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Shlomo Ben David > > It already WARN on it: > - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 > We can make it more strict and give VERIFY -1. > Adding infra-support to open a ticket on it. > We intentionally didn't enforce Verify as default since we wanted to give > time to the hook > to work and see we don't have false positives on it. > On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > > Example: > > https://gerrit.ovirt.org/#/c/71374/ > > > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > > pushed into the 4.1 stable branch > > > > Thanks. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1089) Re: Wrong target milestone bugs should be blocked with -verified on the stable branches
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

eyal edri [Administrator] created OVIRT-1089: ------------------------------------------------ Summary: Re: Wrong target milestone bugs should be blocked with -verified on the stable branches Key: OVIRT-1089 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1089 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: eyal edri [Administrator] Assignee: infra It already WARN on it: - Check TM::#1416309::WARN, wrong target milestone: ovirt-4.2.0 We can make it more strict and give VERIFY -1. Adding infra-support to open a ticket on it. We intentionally didn't enforce Verify as default since we wanted to give time to the hook to work and see we don't have false positives on it. On Mon, Jan 30, 2017 at 3:13 PM, Tal Nisan <tnisan(a)redhat.com> wrote: > Example: > https://gerrit.ovirt.org/#/c/71374/ > > I'd expect the Gerrit hooks to give -1 on verified when a 4.2 bug is > pushed into the 4.1 stable branch > > Thanks. > > _______________________________________________ > Infra mailing list > Infra(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra > > -- Eyal Edri Associate Manager RHV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1088) Block internet access to mirrors.phx.ovirt.org
by Barak Korren (oVirt JIRA) 30 Jan '17

30 Jan '17

Barak Korren created OVIRT-1088: ----------------------------------- Summary: Block internet access to mirrors.phx.ovirt.org Key: OVIRT-1088 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1088 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Barak Korren Assignee: infra mirrors.phx.ovirt.org currently allows HTTP access from the entire internet. It was convenient while it was being deployed, but now it should be changed to allow access only from the PHC data center. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1088) Block internet access to mirrors.phx.ovirt.org
by Barak Korren (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1088?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1088: -------------------------------- Epic Link: OVIRT-403 > Block internet access to mirrors.phx.ovirt.org > ---------------------------------------------- > > Key: OVIRT-1088 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1088 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Barak Korren > Assignee: infra > > mirrors.phx.ovirt.org currently allows HTTP access from the entire internet. It was convenient while it was being deployed, but now it should be changed to allow access only from the PHC data center. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1087) drop gerrit log watch emails in favor or real monitoring
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

eyal edri [Administrator] created OVIRT-1087: ------------------------------------------------ Summary: drop gerrit log watch emails in favor or real monitoring Key: OVIRT-1087 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1087 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra Right now Gerrit sends regular emails from log-watch with various info, such as [1]. We need to go over these alerts and see if some make sense to convert to alerts on nagios and disable the rest. [1]. /changes/67155/revisions/57f6a24d70230c5e7 ... README/reviewed: 2 Time(s) /changes/67587/revisions/807e4950b3a74d127 ... 6f9f5be2/rebase: 1 Time(s) /changes/68315/revisions/182e8209319a41adc ... kefile/reviewed: 2 Time(s) /changes/70704/edit?list: 1 Time(s) /changes/71065/reviewers/1001042: 1 Time(s) /changes/71129/revisions/07edcd447865468bc ... 086f7545/drafts: 2 Time(s) /changes/71315/reviewers/1000458: 1 Time(s) /changes/71337/revisions/3f37d51915b0c7235 ... 829ed631/submit: 1 Time(s) /changes/?q=change:70704+has:draft&O=0: 1 Time(s) /changes/?q=is:open+owner:self&q=is:open+r ... +limit:10&O=881: 2 Time(s) 404 Not Found /changes/55626/detail?O=50004: 1 Time(s) /changes/70594/detail?O=50004: 2 Time(s) /changes/71272/detail?O=50004: 1 Time(s) /gerrit_ui/undefined.cache.js: 1 Time(s) /ovirt-system-tests: 2 Time(s) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-1087) drop gerrit log watch emails in favor or real monitoring
by eyal edri [Administrator] (oVirt JIRA) 30 Jan '17

30 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1087?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1087: --------------------------------------------- Epic Link: OVIRT-403 > drop gerrit log watch emails in favor or real monitoring > -------------------------------------------------------- > > Key: OVIRT-1087 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1087 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > Right now Gerrit sends regular emails from log-watch with various info, such as [1]. > We need to go over these alerts and see if some make sense to convert to alerts on nagios and disable the rest. > [1]. > /changes/67155/revisions/57f6a24d70230c5e7 ... README/reviewed: 2 Time(s) > /changes/67587/revisions/807e4950b3a74d127 ... 6f9f5be2/rebase: 1 Time(s) > /changes/68315/revisions/182e8209319a41adc ... kefile/reviewed: 2 Time(s) > /changes/70704/edit?list: 1 Time(s) > /changes/71065/reviewers/1001042: 1 Time(s) > /changes/71129/revisions/07edcd447865468bc ... 086f7545/drafts: 2 Time(s) > /changes/71315/reviewers/1000458: 1 Time(s) > /changes/71337/revisions/3f37d51915b0c7235 ... 829ed631/submit: 1 Time(s) > /changes/?q=change:70704+has:draft&O=0: 1 Time(s) > /changes/?q=is:open+owner:self&q=is:open+r ... +limit:10&O=881: 2 Time(s) > 404 Not Found > /changes/55626/detail?O=50004: 1 Time(s) > /changes/70594/detail?O=50004: 2 Time(s) > /changes/71272/detail?O=50004: 1 Time(s) > /gerrit_ui/undefined.cache.js: 1 Time(s) > /ovirt-system-tests: 2 Time(s) -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #432 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 30 Jan '17

30 Jan '17

------=_Part_179_786417210.1485688329714 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/432/, Build Number: 432, Build Status: FAILURE ------=_Part_179_786417210.1485688329714--

1 1

oVirt infra daily report - unstable production jobs - 215
by jenkins＠jenkins.phx.ovirt.org 29 Jan '17

29 Jan '17

------=_Part_193_501168291.1485730806584 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/215//artifact/exported-a… Cheers, Jenkins ------=_Part_193_501168291.1485730806584 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 29/01/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt_3.6_he-system-tests/">ovirt_3.6_he-system-tests</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_193_501168291.1485730806584--

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by Yaniv Kaul (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] Yaniv Kaul commented on OST-39: ------------------------------- 0. I think it's time to understand if we want to use Lago for Kubevirt or not. I prefer vagrant - it's more common, works out of the box on both Ubuntu and possibly other operating systems (does it have nested virt on Mac or Windows?). I would like to believe that moving to vagrant is actually a good opportunity to start afresh. Lago is not killed by it, and will remain relevant for OST. 1. Ansible is supported today in vagrant. I believe a fair start of support exists in Lago as well - but as Barak pointed out, probably need a bit of Cloud-Init work too perhaps - not sure. Engine is not containerized for real yet. Once it does, we'll probably deploy it via standard Pod deployment options (saw today ansible-containers, for example - sounds neat). > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] commented on OST-39: ---------------------------------------------- This is the tool we're using for tracking issues for OST, so its the right place, if needed we can have a trello card pointing to this ticket. 0. Lago. I don't think that the fact Vagrant was used for POC KubeVirt alone is a major advantage to re-do all the work we've done to make OST run with Lago, Moving to Vagrant will mean investing a lot of efforts and resources ( which we don't have, looking at the Lago+OST headcount ATM ) into making something we already have working for little value IMO and will delay significantly the work to support KubeVirt. We can consider it once we'll have a full time maintainer for Lago/OST. 1. Once we support Ansible as deploy scripts in OST, which shouldn't be hard after the recent merges to Lago, we can just use the existing Kubenetes playbooks, not sure how using Vagrant makes it simpler. Ansible for engine - not sure how/what we'll need, but [~fdeutsch] provided us with POD definitions, I'm guessing once you have Kubenetes its just a matter of running / deploying the engine container? ( so according to the request we should have available engine & vdsm in containers, otherwise I didn't understand the request ) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by Yaniv Kaul (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] Yaniv Kaul commented on OST-39: ------------------------------- [~eedri] - too many items there, I think. We should probably document it in KubeVirt's trello and not here. 0. Do we use Lago as is, or vagrant? Unclear to me, and I do see a nice advantage for the community using vagrant. 1. Ansible installing K8S - makes sense to me. This is quite integrated into vagrant and is easy to do (though requires Ansible on Host L0) in Lago. Do we have Ansible to install Engine? Quite possibly from QCI - we should utilize that - but it's not within a Container - Engine is not yet containerized (production-ready, at least) 3. Good point about Add Host. Donno yet... 4. ACK 5. ACK. > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OST-39) Run OST against vdsm+Engine on kubernetes
by eyal edri [Administrator] (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OST-39?page=com.atlassian.jira.plug… ] eyal edri [Administrator] commented on OST-39: ---------------------------------------------- [~fdeutsch] Just to emphasis the scope and requirements, let me re-iterate on what we agreed on the email: A new OST suite will be created which will run the same tests run today in basic suite, the difference will be: 1. Replace deploy scripts for engine + storage with Ansible playbook which will install Kubernetes 2. The Ansible playbook will also need to deploy engine + vdsm as containers in PODS once Kubernetes will be running 3. Not sure how 'add host' should work - will VDSM come ready in a container and already connect to the engine or we'll still need to run 'add host' command to add it? or an alternative 'add host' command. 4. Kubernetes will be running on VMs created by Lago 5. We will consider to use Atomic as OS for the VMs, but CentOS should work as well as starting point. Please confirm I'm not talking nonsense and we can continue to move towards this goal :) > Run OST against vdsm+Engine on kubernetes > ----------------------------------------- > > Key: OST-39 > URL: https://ovirt-jira.atlassian.net/browse/OST-39 > Project: oVirt system tests > Issue Type: New Feature > Reporter: Fabian Deutsch > Assignee: infra > Priority: Highest > Labels: kubevirt > > Hey, > Yaniv Bronheim is building containers for vdsm and engine. > Lago should become capable of running OST against this setup. > The basic flow is: > 1. Normal CentOS > 2. Install kubernetes > 3. Deploy engine and vdsm pods > The pod definitions are here: > https://gerrit.ovirt.org/gitweb?p=ovirt-container-engine.git;a=tree > https://gerrit.ovirt.org/gitweb?p=ovirt-container-node.git;a=tree > A similar script can be found here: > https://github.com/kubevirt/demo/blob/master/data/bootstrap-kubevirt.sh > But this script is deploying kubevirt, instead of the engine + vdsm container. -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #430 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 29 Jan '17

29 Jan '17

------=_Part_173_1799120868.1485680413376 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/430/, Build Number: 430, Build Status: FAILURE ------=_Part_173_1799120868.1485680413376--

1 1

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-904: -------------------------------------------- Resolution: Done Status: Done (was: Blocked) Address via moving PatternFly to oVirt standard CI > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-904) False CI-1 due to unreachable copr-be.cloud.fedoraproject.org
by eyal edri [Administrator] (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-904?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-904: ------------------------------------------------- OK, I'll close this ticket then and we'll follow up on progress to move Patternfly and friends out of copr and into oVirt repo in their own tickets. > False CI-1 due to unreachable copr-be.cloud.fedoraproject.org > ------------------------------------------------------------- > > Key: OVIRT-904 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-904 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > Many patches on > https://gerrit.ovirt.org/#/q/topic:passthroughMigration fail CI due to > failure: repodata/repomd.xml from patternfly: [Errno 256] No more > mirrors to try. > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-…: > [Errno 14] curl#7 - "Failed connect to > copr-be.cloud.fedoraproject.org:80; No route to host" > http://copr-be.cloud.fedoraproject.org/results/patternfly/patternfly1/epel-… -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0

[JIRA] (OVIRT-753) ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands
by eyal edri [Administrator] (oVirt JIRA) 29 Jan '17

29 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-753?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-753: -------------------------------------------- Resolution: Incomplete Status: Done (was: Blocked) no reply since Nov, please re-open if still relevant. > ovirt-appliance_master_build-artifacts-el7-x86_64 is ignoring failed commands > ----------------------------------------------------------------------------- > > Key: OVIRT-753 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-753 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: infra > > In: > http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-el7-x86… > After appliance shutdown: > *00:15:44.383* [[ -n "1" ]] && [[ "$(virt-sparsify --help)" =~ > --in-place ]] && ( virt-sparsify --in-place > ovirt-engine-appliance.qcow2 ; ln ovirt-engine-appliance.qcow2 > ovirt-engine-appliance.qcow2.sparse ; )*00:25:53.734* virt-sparsify: > error: libguestfs error: guestfs_launch failed.*00:25:53.735* This > usually means the libguestfs appliance failed to start or > crashed.*00:25:53.735* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:25:53.735* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:25:53.735* bug report or message to the libguestfs mailing list. > The job should have failed here. Instead, the job continues and fails in a > later stage: > *00:33:01.284* ls -shal ovirt-engine-appliance.ova*00:33:01.287* 1.4G > -rwxr-xr-x. 1 root root 1.4G Oct 6 14:13 > ovirt-engine-appliance.ova*00:33:01.288* echo "all" appliance > done*00:33:01.290* all appliance done*00:33:01.291* + make > check*00:33:01.299* make -f image-tools/build.mk > ovirt-engine-appliance-manifest-rpm*00:33:01.305* make[1]: Entering > directory `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:33:01.305* > guestfish --ro -i -a ovirt-engine-appliance.qcow2 sh 'rpm -qa | sort > -u' > ovirt-engine-appliance-manifest-rpm*00:41:58.044* libguestfs: > error: appliance closed the connection unexpectedly.*00:41:58.044* > This usually means the libguestfs appliance crashed.*00:41:58.044* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.045* > for information about how to debug libguestfs and report > bugs.*00:41:58.045* libguestfs: error: guestfs_launch > failed.*00:41:58.045* This usually means the libguestfs appliance > failed to start or crashed.*00:41:58.045* See > http://libguestfs.org/guestfs-faq.1.html#debugging-libguestfs*00:41:58.046* > or run 'libguestfs-test-tool' and post the *complete* output into > a*00:41:58.046* bug report or message to the libguestfs mailing > list.*00:41:58.059* make[1]: *** [ovirt-engine-appliance-manifest-rpm] > Error 1*00:41:58.059* make[1]: Leaving directory > `/home/jenkins/workspace/ovirt-appliance_master_build-artifacts-el7-x86_64/ovirt-appliance/engine-appliance'*00:41:58.060* > make: *** [ovirt-engine-appliance-manifest-rpm] Error 2*00:41:58.065* > Took 2325 seconds > wasting 20 minutes of jenkins slave time testing something already known > broken. > While working on fixing this job, please investigate while it's failing and > open a separate issue or bugzilla for it. > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com > <https://www.redhat.com/it/about/events/red-hat-open-source-day-2016> -- This message was sent by Atlassian JIRA (v1000.718.3#100026)

1 0