- Infra - oVirt List Archives

Re: Change in ovirt-setup-lib[master]: hostname: Support IPv6
by Yedidyah Bar David 19 Jul '18

19 Jul '18

On Thu, Jul 19, 2018 at 9:31 AM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI <jenkins(a)ovirt.org>: > > Jenkins CI has posted comments on this change. > > Change subject: hostname: Support IPv6 > ...................................................................... > > > Patch Set 11: Continuous-Integration-1 > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-setup-lib_master_check-patch-el7-x86_64/… : FAILURE https://jenkins.ovirt.org/job/ovirt-setup-lib_master_check-patch-el7-x86_64… ends with: + yum -y install otopi Error: Nothing to do Took 2 seconds Searched a bit, read a bit of yum's code, decided to ignore for now. Retriggered, and it failed again the same way. Another patch did pass. I assume it's something related to the mock cache and some very specific condition, for which yum does not provide enough details. Tried a bit to look at the relevant code, didn't fully understand. Normally yum says "Nothing to do" and does not fail, if it has nothing to do. For now I'll just remove this command. Sandro added it some months ago to work around some problem in CI. Hopefully it was solved since. > > http://jenkins.ovirt.org/job/ovirt-setup-lib_master_check-patch-fc28-x86_64… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/92832 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-Project: ovirt-setup-lib > Gerrit-Branch: master > Gerrit-MessageType: comment > Gerrit-Change-Id: I4667c96b173308a429ce5992d5478dc47d500984 > Gerrit-Change-Number: 92832 > Gerrit-PatchSet: 11 > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Asaf Rachmani <arachman(a)redhat.com> > Gerrit-Reviewer: Dominik Holler <dholler(a)redhat.com> > Gerrit-Reviewer: Gal Zaidman <gzaidman(a)redhat.com> > Gerrit-Reviewer: Ido Rosenzwig <irosenzw(a)redhat.com> > Gerrit-Reviewer: Jenkins CI <jenkins(a)ovirt.org> > Gerrit-Reviewer: Lev Veyde <lveyde(a)redhat.com> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Simone Tiraboschi <stirabos(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-Comment-Date: Thu, 19 Jul 2018 06:31:12 +0000 > Gerrit-HasComments: No -- Didi

1 0

[JIRA] (OVIRT-2346) Find a way to identify the daemon/client that created a given container
by Daniel Belenky (oVirt JIRA) 18 Jul '18

18 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2346?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2346: ---------------------------------- Description: In order to properly clean containers, we need a way to recognize which containers were created from clients that are running in other containers. We need to see if this can be achieved somehow by using labels > Find a way to identify the daemon/client that created a given container > ----------------------------------------------------------------------- > > Key: OVIRT-2346 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2346 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > In order to properly clean containers, we need a way to recognize which containers were created from clients that are running in other containers. We need to see if this can be achieved somehow by using labels -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2346) Find a way to identify the daemon/client that created a given container
by Daniel Belenky (oVirt JIRA) 18 Jul '18

18 Jul '18

Daniel Belenky created OVIRT-2346: ------------------------------------- Summary: Find a way to identify the daemon/client that created a given container Key: OVIRT-2346 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2346 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2346) Find a way to identify the daemon/client that created a given container
by Daniel Belenky (oVirt JIRA) 18 Jul '18

18 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2346?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2346: ---------------------------------- Epic Link: OVIRT-2326 > Find a way to identify the daemon/client that created a given container > ----------------------------------------------------------------------- > > Key: OVIRT-2346 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2346 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[CQ]: 93132, 2 (engine-db-query) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jul '18

18 Jul '18

A system test invoked by the "ovirt-master" change queue including change 93132,2 (engine-db-query) failed. However, this change seems not to be the root cause for this failure. Change 93128,2 (engine-db-query) 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 93128,2 (engine-db-query) 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/93132/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93128/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8733/

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-ansible-suite-4.2 - Build # 387 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jul '18

18 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/… Build Number: 387 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #387 [Milan Zamazal] Add basic-suite-compat-master ----------------- Failed Tests: ----------------- All tests passed

1 1

oVirt infra daily report - unstable production jobs - 525
by jenkins＠jenkins.phx.ovirt.org 18 Jul '18

18 Jul '18

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

1 0

[CQ]: 93130, 1 (engine-db-query) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jul '18

18 Jul '18

A system test invoked by the "ovirt-master" change queue including change 93130,1 (engine-db-query) failed. However, this change seems not to be the root cause for this failure. Change 93128,2 (engine-db-query) 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 93128,2 (engine-db-query) 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/93130/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93128/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8730/

1 0

[CQ]: 93129, 2 (engine-db-query) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jul '18

18 Jul '18

A system test invoked by the "ovirt-master" change queue including change 93129,2 (engine-db-query) failed. However, this change seems not to be the root cause for this failure. Change 93128,2 (engine-db-query) 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 93128,2 (engine-db-query) 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/93129/2 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/93128/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8728/

1 0

[CQ]: 93128,2 (engine-db-query) failed "ovirt-master" system tests
by oVirt Jenkins 18 Jul '18

18 Jul '18

Change 93128,2 (engine-db-query) 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/93128/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8727/

1 0