Change in stdci-staging[master]: Check timeout functionality
by review@gerrit-staging.phx.ovirt.org
From Daniel Belenky <dbelenky(a)redhat.com>:
Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/213 )
Change subject: Check timeout functionality
......................................................................
Patch Set 1:
ci test please
--
To view, visit https://gerrit-staging.phx.ovirt.org/213
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings
Gerrit-Project: stdci-staging
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7
Gerrit-Change-Number: 213
Gerrit-PatchSet: 1
Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>
Gerrit-Comment-Date: Thu, 06 Sep 2018 12:32:06 +0000
Gerrit-HasComments: No
6 years, 2 months
Change in stdci-staging[master]: Check timeout functionality
by review@gerrit-staging.phx.ovirt.org
From Daniel Belenky <dbelenky(a)redhat.com>:
Hello Jenkins CI,
I'd like you to reexamine a change. Please visit
https://gerrit-staging.phx.ovirt.org/213
to look at the new patch set (#2).
Change subject: Check timeout functionality
......................................................................
Check timeout functionality
Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7
Signed-off-by: Daniel Belenky <dbelenky(a)redhat.com>
---
A automation/check-patch.do-not-timeout.sh
A automation/check-patch.do-timeout.sh
M stdci.yaml
3 files changed, 19 insertions(+), 3 deletions(-)
git pull ssh://gerrit-staging.phx.ovirt.org:29418/stdci-staging refs/changes/13/213/2
--
To view, visit https://gerrit-staging.phx.ovirt.org/213
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings
Gerrit-Project: stdci-staging
Gerrit-Branch: master
Gerrit-MessageType: newpatchset
Gerrit-Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7
Gerrit-Change-Number: 213
Gerrit-PatchSet: 2
Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>
6 years, 2 months
Change in stdci-staging[master]: Check timeout functionality
by review@gerrit-staging.phx.ovirt.org
From Daniel Belenky <dbelenky(a)redhat.com>:
Daniel Belenky has posted comments on this change. ( https://gerrit-staging.phx.ovirt.org/213 )
Change subject: Check timeout functionality
......................................................................
Patch Set 1:
ci test please
--
To view, visit https://gerrit-staging.phx.ovirt.org/213
To unsubscribe, visit https://gerrit-staging.phx.ovirt.org/settings
Gerrit-Project: stdci-staging
Gerrit-Branch: master
Gerrit-MessageType: comment
Gerrit-Change-Id: I8264e2efd72cf4c969dd9d2a149a3fbd45f6feb7
Gerrit-Change-Number: 213
Gerrit-PatchSet: 1
Gerrit-Owner: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Daniel Belenky <dbelenky(a)redhat.com>
Gerrit-Reviewer: Jenkins CI <infra(a)ovirt.org>
Gerrit-Comment-Date: Thu, 06 Sep 2018 11:45:31 +0000
Gerrit-HasComments: No
6 years, 2 months
[JIRA] (OVIRT-2479) CQ Failure - Alot of ovirt-hosted-engine-setup
messages.
by Dafna Ron (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2479?page=com.atlassian.jir... ]
Dafna Ron updated OVIRT-2479:
-----------------------------
Issue Type: Bug (was: Outage)
> CQ Failure - Alot of ovirt-hosted-engine-setup messages.
> --------------------------------------------------------
>
> Key: OVIRT-2479
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2479
> Project: oVirt - virtualization made easy
> Issue Type: Bug
> Components: Change Queue, OST
> Reporter: Ehud Yonasi
> Assignee: infra
> Labels: cq-issue-traking, ost_failures
>
> Since 3rd september there were alot of changes coming out of the blue to CQ about ovirt-hosted-engine-setup.
> while investigating why it happened, I found out that the remote repo was deleted somehow and was restored.
> That restoration caused all the project patches all-at-once triggers hundreds of jobs in build-art + CQ.
> In order to recover from that situation i had to find the last patch of that project and asked for a re-merge (ci re-merge please).
> After that change and multiple runs of CQ it passed.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months
[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 447
- Failure!
by jenkins@jenkins.phx.ovirt.org
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/447/
Build Number: 447
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #447
[Gal Ben Haim] Adding dr suite
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 004_basic_sanity.snapshot_merge
Error Message:
status: 409
reason: Conflict
detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0.
Stack Trace:
Traceback (most recent call last):
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 69, in wrapper
return func(prefix.virt_env.engine_vm().get_api(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt-system-tests_hc-basic-suite-4.2/ovirt-system-tests/hc-basic-suite-4.2/test-scenarios/004_basic_sanity.py", line 200, in snapshot_merge
api.vms.get(VM0_NAME).snapshots.list()[-2].delete()
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/brokers.py", line 34001, in delete
headers={"Correlation-Id":correlation_id,"Content-type":None}
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 57, in delete
return self.request('DELETE', url, body, headers, cls=cls)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/proxy.py", line 122, in request
persistent_auth=self.__persistent_auth
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 79, in do_request
persistent_auth)
File "/usr/lib/python2.7/site-packages/ovirtsdk/infrastructure/connectionspool.py", line 162, in __do_request
raise errors.RequestError(response_code, response_reason, response_body)
RequestError:
status: 409
reason: Conflict
detail: Cannot remove Snapshot. Snapshot is currently being created for VM vm0.
6 years, 2 months
[oVirt Jenkins] ovirt-system-tests_compat-4.2-suite-master - Build
# 137 - Failure!
by jenkins@jenkins.phx.ovirt.org
Project: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/
Build: http://jenkins.ovirt.org/job/ovirt-system-tests_compat-4.2-suite-master/137/
Build Number: 137
Build Status: Failure
Triggered By: Started by timer
-------------------------------------
Changes Since Last Success:
-------------------------------------
Changes for Build #137
[Gal Ben Haim] Adding dr suite
[Barak Korren] Remove the populate_mock function from mock_runner
[Daniel Belenky] mock_runner: store shell cmd in a variable
[Barak Korren] mock_runner: Added timeout param
[Barak Korren] Make whitelist repo configurable via env vars
[Daniel Belenky] stdci_runner: let mock_runner manage timeout
[Greg Sheremeta] remove 4.1 change queue from ovirt-engine-nodejs config
-----------------
Failed Tests:
-----------------
1 tests failed.
FAILED: 004_basic_sanity.verify_suspend_resume_vm0_42
Error Message:
0 != 1
-------------------- >> begin captured logging << --------------------
lago.ssh: DEBUG: start task:5c4788eb-8a69-4127-878e-8d49d9fb07c7:Get ssh client for lago-compat-4-2-suite-master-host-0:
lago.ssh: DEBUG: end task:5c4788eb-8a69-4127-878e-8d49d9fb07c7:Get ssh client for lago-compat-4-2-suite-master-host-0:
lago.ssh: DEBUG: Running 012e8ff2 on lago-compat-4-2-suite-master-host-0: awk 'BEGIN { n = 0; } $1 + " " + $2 > "IOError: [Errno" && $0 ~ /START create\(.*memoryDumpVolume/ { n = n + 1; } END { print n; }' /var/log/vdsm/vdsm.log
lago.ssh: DEBUG: Command 012e8ff2 on lago-compat-4-2-suite-master-host-0 returned with 0
lago.ssh: DEBUG: Command 012e8ff2 on lago-compat-4-2-suite-master-host-0 output:
0
--------------------- >> end captured logging << ---------------------
Stack Trace:
File "/usr/lib64/python2.7/unittest/case.py", line 369, in run
testMethod()
File "/usr/lib/python2.7/site-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 142, in wrapped_test
test()
File "/usr/lib/python2.7/site-packages/ovirtlago/testlib.py", line 60, in wrapper
return func(get_test_prefix(), *args, **kwargs)
File "/home/jenkins/workspace/ovirt-system-tests_compat-4.2-suite-master/ovirt-system-tests/compat-4.2-suite-master/test-scenarios/004_basic_sanity.py", line 1140, in verify_suspend_resume_vm0
nt.assert_equals(log_line_count('START create\(.*' + identifier), 1)
File "/usr/lib64/python2.7/unittest/case.py", line 553, in assertEqual
assertion_func(first, second, msg=msg)
File "/usr/lib64/python2.7/unittest/case.py", line 546, in _baseAssertEqual
raise self.failureException(msg)
'0 != 1\n-------------------- >> begin captured logging << --------------------\nlago.ssh: DEBUG: start task:5c4788eb-8a69-4127-878e-8d49d9fb07c7:Get ssh client for lago-compat-4-2-suite-master-host-0:\nlago.ssh: DEBUG: end task:5c4788eb-8a69-4127-878e-8d49d9fb07c7:Get ssh client for lago-compat-4-2-suite-master-host-0:\nlago.ssh: DEBUG: Running 012e8ff2 on lago-compat-4-2-suite-master-host-0: awk \'BEGIN { n = 0; } $1 + " " + $2 > "IOError: [Errno" && $0 ~ /START create\\(.*memoryDumpVolume/ { n = n + 1; } END { print n; }\' /var/log/vdsm/vdsm.log\nlago.ssh: DEBUG: Command 012e8ff2 on lago-compat-4-2-suite-master-host-0 returned with 0\nlago.ssh: DEBUG: Command 012e8ff2 on lago-compat-4-2-suite-master-host-0 output:\n 0\n\n--------------------- >> end captured logging << ---------------------'
6 years, 2 months
[JIRA] (OVIRT-2480) ovirt-srv04 out of disk space
by Evgheni Dereveanchin (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2480?page=com.atlassian.jir... ]
Evgheni Dereveanchin reassigned OVIRT-2480:
-------------------------------------------
Assignee: Evgheni Dereveanchin (was: infra)
> ovirt-srv04 out of disk space
> -----------------------------
>
> Key: OVIRT-2480
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2480
> Project: oVirt - virtualization made easy
> Issue Type: Improvement
> Reporter: Evgheni Dereveanchin
> Assignee: Evgheni Dereveanchin
>
> ovirt-srv04 ran out of disk space again. Noticed this while working on monitoring for this box. Need to confirm what is using disk space and fix the issue. There are 4 kubevirt_kubevirt_standard-check-pr jobs currently running in containers on this hosts so they are likely to fail.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months
[JIRA] (OVIRT-2480) ovirt-srv04 out of disk space
by Evgheni Dereveanchin (oVirt JIRA)
Evgheni Dereveanchin created OVIRT-2480:
-------------------------------------------
Summary: ovirt-srv04 out of disk space
Key: OVIRT-2480
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2480
Project: oVirt - virtualization made easy
Issue Type: Improvement
Reporter: Evgheni Dereveanchin
Assignee: infra
ovirt-srv04 ran out of disk space again. Noticed this while working on monitoring for this box. Need to confirm what is using disk space and fix the issue. There are 4 kubevirt_kubevirt_standard-check-pr jobs currently running in containers on this hosts so they are likely to fail.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100091)
6 years, 2 months