- Infra - oVirt List Archives

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3281 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xf41k.

1 0

[oVirt CI] standard-enqueue - Build #18857 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/18857/ Build Name: #18857 Build Description: Gerrit: 97088 - ovirt-wgt (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/97088 - title: build: ovirt-wgt-4.3-1 - project: ovirt-wgt - branch: master - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 2

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3279 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-pm0qz.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3279 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-0rjlq.

1 0

[oVirt CI] standard-enqueue - Build #18853 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Build: http://jenkins.ovirt.org/job/standard-enqueue/18853/ Build Name: #18853 Build Description: Gerrit: 97219 - ovirt-guest-agent (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/97219 - title: automation: improvements - project: ovirt-guest-agent - branch: master - author: Sandro Bonazzola <sbonazzo(a)redhat.com>

1 1

[CQ]: 97222, 1 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 23 Jan '19

23 Jan '19

Change 97222,1 (ovirt-hosted-engine-ha) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97222/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12412/

2 1

[CQ]: 97205, 1 (ovirt-guest-agent) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 23 Jan '19

23 Jan '19

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

2 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3275 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-djxvj.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3275 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-h8s23.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3274 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-zw47x.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3270 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-txvc3.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

Failed to run project_setup.sh for: #3270 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cz6ws.

1 0

[CQ]: 97203,1 (ovirt-guest-agent) failed "ovirt-master" system tests
by oVirt Jenkins 23 Jan '19

23 Jan '19

Change 97203,1 (ovirt-guest-agent) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/97203/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/12397/

1 0

oVirt infra daily report - unstable production jobs - 713
by jenkins＠jenkins.phx.ovirt.org 23 Jan '19

23 Jan '19

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/713//artifact/exported-a… Cheers, Jenkins

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3269 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-nkk3w.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3269 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-fpfft.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3267 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-7c1ns.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3266 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-ddt31.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3265 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-11f0p.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3265 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-4xqfs.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3264 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-l82sm.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3260 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-8v15k.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3260 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-rpqnt.

1 0

Change in barak-test[master]: jenkins integ test
by review＠gerrit-staging.phx.ovirt.org 22 Jan '19

22 Jan '19

From Evgheni Dereveanchin <ederevea(a)redhat.com>: Evgheni Dereveanchin has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/17 ) Change subject: jenkins integ test ...................................................................... Patch Set 1: test -- To view, visit https://gerrit-staging.phx.ovirt.org/17 To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings Gerrit-Project: barak-test Gerrit-Branch: master Gerrit-MessageType: comment Gerrit-Change-Id: I50acc69c8c5b6b3e03f3ced23d72c883ac4db2c2 Gerrit-Change-Number: 17 Gerrit-PatchSet: 1 Gerrit-Owner: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Evgheni Dereveanchin <ederevea(a)redhat.com> Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org> Gerrit-Comment-Date: Tue, 22 Jan 2019 18:43:31 +0000 Gerrit-HasComments: No

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3258 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6xgc5.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3258 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-xxbtc.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3258 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-k6gfp.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3257 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-r5t2d.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3256 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cf95t.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3255 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-1zbk5.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3257 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6r5qb.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3255 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-k09kw.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3249 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-cntlg.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3249 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-5h3j3.

1 0

[JIRA] (OVIRT-2655) ovirt-provider-ovn is failing on ovirt-4.2
by Dafna Ron (oVirt JIRA) 22 Jan '19

22 Jan '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2655?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2655: ----------------------------- Resolution: Fixed Status: Done (was: To Do) > ovirt-provider-ovn is failing on ovirt-4.2 > ------------------------------------------ > > Key: OVIRT-2655 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2655 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Priority: Highest > Labels: ost_code_regression, ost_failures > > We have a failure in ovirt-provider-ovn. > patch responsible is: > https://gerrit.ovirt.org/#/c/96926/ - ip_version is mandatory on POSTs > build: > http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/3742/ > {noformat} > 2019-01-18 00:45:01,435 root Missing 'ip_version' attribute > Traceback (most recent call last): > File "/usr/share/ovirt-provider-ovn/handlers/base_handler.py", line 134, in _handle_request > method, path_parts, content > File "/usr/share/ovirt-provider-ovn/handlers/selecting_handler.py", line 175, in handle_request > return self.call_response_handler(handler, content, parameters) > File "/usr/share/ovirt-provider-ovn/handlers/neutron.py", line 36, in call_response_handler > return response_handler(ovn_north, content, parameters) > File "/usr/share/ovirt-provider-ovn/handlers/neutron_responses.py", line 154, in post_subnets > subnet = nb_db.add_subnet(received_subnet) > File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 74, in wrapper > validate_rest_input(rest_data) > File "/usr/share/ovirt-provider-ovn/neutron/neutron_api_mappers.py", line 596, in validate_add_rest_input > raise BadRequestError('Missing \'ip_version\' attribute') > BadRequestError: Missing 'ip_version' attribute > {noformat} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100098)

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-zml27.

1 2

Build failed in Jenkins: deploy-to_ovirt-master_tested #6195
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

See <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/6195/display/red…> ------------------------------------------ Started by upstream project "ovirt-appliance_master_build-artifacts-fc28-x86_64" build number 196 originally caused by: Started by timer [EnvInject] - Loading node environment variables. Building remotely on vm0010.workers-phx.ovirt.org (el7 phx nested) in workspace <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/> [ssh-agent] Looking for ssh-agent implementation... [ssh-agent] Exec ssh-agent (binary ssh-agent on a remote machine) $ ssh-agent SSH_AUTH_SOCK=/tmp/ssh-RjQCi8yNXHBi/agent.2679 SSH_AGENT_PID=2681 [ssh-agent] Started. Running ssh-add (command line suppressed) Identity added: <http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private_…> (<http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/ws/@tmp/private_…)> [ssh-agent] Using credentials deploy-ovirt-experimental (SSH key for deploying to the tested repo) [deploy-to_ovirt-master_tested] $ /bin/bash -xe /tmp/jenkins2132542383419911218.sh + [[ http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… == '' ]] + queue_name=ovirt-master + ssh -o StrictHostKeyChecking=no deploy-ovirt-experimental(a)resources.ovirt.org + echo repo-extra-dir:master + echo http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Pseudo-terminal will not be allocated because stdin is not a terminal. + BASE_DIR=/srv/resources/repos/ovirt/tested + PUBLISH_MD_COPIES=50 + main + local tmp_dir + mkdir -p /srv/resources/repos/ovirt/tested ++ mktemp -d /srv/resources/repos/ovirt/tested/.deploy.XXXXXXXXXX Collecting packages + tmp_dir=/srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM + trap 'rm -rf '\''/srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM'\''' EXIT HUP + echo 'Collecting packages' + collect_packages /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM + local repoman_dst=/srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM + repoman --temp-dir generate-in-repo --option main.allowed_repo_paths=/srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM --option main.on_empty_source=warn /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM add conf:stdin 2019-01-22 09:36:29,462::INFO::repoman.cmd:: 2019-01-22 09:36:29,462::INFO::repoman.cmd::Adding artifacts to the repo /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM 2019-01-22 09:36:29,463::INFO::repoman.common.repo::Adding repo extra dir master 2019-01-22 09:36:29,468::INFO::repoman.common.stores.RPM::Loading repo /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/master 2019-01-22 09:36:29,468::INFO::repoman.common.stores.RPM::Repo /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/master loaded 2019-01-22 09:36:29,471::INFO::repoman.common.stores.iso::Loading repo /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/master 2019-01-22 09:36:29,471::INFO::repoman.common.stores.iso::Repo /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/master loaded 2019-01-22 09:36:29,490::INFO::repoman.common.repo::Resolving artifact source http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… 2019-01-22 09:36:29,674::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '406', 'content-type': 'text/html;charset=utf-8', 'date': 'Tue, 22 Jan 2019 09:36:29 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-01-22 09:36:31,733::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '406', 'content-type': 'text/html;charset=utf-8', 'date': 'Tue, 22 Jan 2019 09:36:31 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-01-22 09:36:33,789::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '406', 'content-type': 'text/html;charset=utf-8', 'date': 'Tue, 22 Jan 2019 09:36:33 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-01-22 09:36:35,841::ERROR::repoman.common.sources.jenkins::URL: http://jenkins.ovirt.org/job/ovirt-appliance_master_build-artifacts-fc28-x8… Status: 503 Reason: Service Unavailable Headers: {'cache-control': 'no-cache,no-store,must-revalidate', 'connection': 'close', 'content-encoding': 'gzip', 'content-length': '406', 'content-type': 'text/html;charset=utf-8', 'date': 'Tue, 22 Jan 2019 09:36:35 GMT', 'expires': '0', 'server': 'Jetty(9.4.z-SNAPSHOT)', 'via': '1.1 jenkins.phx.ovirt.org', 'x-content-type-options': 'nosniff'} Body: <!DOCTYPE html><html lang="en-US"><head><title>Starting Jenkins</title><meta name="ROBOTS" content="NOFOLLOW" /><link rel="stylesheet" href="/css/simple-page.css" type="text/css" /><link rel="stylesheet" href="/css/simple-page.theme.css" type="text/css" /><link rel="stylesheet" href="/css/loading.css" type="text/css" /></head><body><div class="simple-page" role="main"><div class="modal signup"><div class="signupIntroDefault"><div class="logo"></div><h1 class="loading"> Please wait while Jenkins is getting ready to work <span>.</span><span>.</span><span>.</span></h1><p>Your browser will reload automatically when Jenkins is ready.</p></div></div></div><script src="/scripts/loading.js" type="text/javascript"></script><script>safeRedirector(window.location.href);</script></body></html> 2019-01-22 09:36:37,844::ERROR::repoman.cmd:: 2019-01-22 09:36:37,844::ERROR::repoman.cmd::Error while adding conf:stdin 2019-01-22 09:36:37,846::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/.lago_tmp/tmpvzF6LD/tmp5Mwb6s 2019-01-22 09:36:37,847::INFO::repoman.common.repo::Cleaning up temporary dir /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM/.lago_tmp/tmpvzF6LD + rm -rf /srv/resources/repos/ovirt/tested/.deploy.dCMV43gElM Build step 'Execute shell' marked build as failure $ ssh-agent -k unset SSH_AUTH_SOCK; unset SSH_AGENT_PID; echo Agent pid 2681 killed; [ssh-agent] Stopped.

1 1

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-5vtbg.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-4nhxc.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-8rdsd.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-jjwv4.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-r55qk.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-lfk6j.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-lm87d.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3247 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-td578.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-zsqvx.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3245 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-w0g8r.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3245 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-6r8lh.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-qwkk0.

1 0

[JENKINS] Failed to setup proejct kubevirt_kubevirt_standard-check-pr
by jenkins＠jenkins.phx.ovirt.org 22 Jan '19

22 Jan '19

Failed to run project_setup.sh for: #3244 kubevirt [check-patch]. It probably means that docker_cleanup.py failed. This step doesn't fail the job, but we do collect data about such failures to find the root cause. Infra owner, ensure that we're not running out of disk space on openshift-kubevirt-org-3grdk.

1 0