- Infra - oVirt List Archives

[CQ]: 92590,7 (ovirt-engine) failed "ovirt-4.2" system tests
by oVirt Jenkins 02 Jul '18

02 Jul '18

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

2 1

[CQ]: 92202, 14 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 02 Jul '18

02 Jul '18

Change 92202,14 (ovirt-provider-ovn) 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/92202/14 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8515/

2 1

[CQ]: 92363, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Jul '18

02 Jul '18

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

2 1

[CQ]: 92289, 12 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Jul '18

02 Jul '18

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

2 1

[CQ]: 92363, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Jul '18

02 Jul '18

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

2 1

[JIRA] (OVIRT-2247) Improve the CI of KubeVirt related projects
by Eyal Edri (oVirt JIRA) 02 Jul '18

02 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2247?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2247: ---------------------------------- I think it can be ( at least for starts ) a component or Label. We can break it into 2 Epics current: 1. Add CI for KubeVirt-APB, which includes 2248. 2. Add CI for KubeVirt-Ansible, which includes 2258, 2260 3. Not sure we need to rebrand ovirt-infra as oVirt might need containers storage at some point, so maybe open a new docker hub container for kubeVirt-CI? we need to consule on kubevirt ml, but maybe kubevirt-integration? > Improve the CI of KubeVirt related projects > ------------------------------------------- > > Key: OVIRT-2247 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2247 > Project: oVirt - virtualization made easy > Issue Type: Epic > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2272) 07.2018 - Jenkins data partition running out of disk space
by Evgheni Dereveanchin (oVirt JIRA) 02 Jul '18

02 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2272?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2272: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > 07.2018 - Jenkins data partition running out of disk space > ---------------------------------------------------------- > > Key: OVIRT-2272 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2272 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The jenkins disk was increased last month ( OVIRT-1968 ) yet we are at critical levels again. > Opening a new ticket to investigate what's going ong and fix retention if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2272) 07.2018 - Jenkins data partition running out of disk space
by Evgheni Dereveanchin (oVirt JIRA) 02 Jul '18

02 Jul '18

Evgheni Dereveanchin created OVIRT-2272: ------------------------------------------- Summary: 07.2018 - Jenkins data partition running out of disk space Key: OVIRT-2272 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2272 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The jenkins disk was increased last month ( OVIRT-1968 ) yet we are at critical levels again. Opening a new ticket to investigate what's going ong and fix retention if needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2250) update foreman certificate
by Evgheni Dereveanchin (oVirt JIRA) 02 Jul '18

02 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2250?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2250: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > update foreman certificate > -------------------------- > > Key: OVIRT-2250 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2250 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > Puppet agents print the following warning: > Warning: Certificate 'foreman.ovirt.org' will expire on 2018-07-02T13:50:12UTC > The CA certificate was re-generated in OVIRT-1994, now it's time to replace the puppetmaster cert as well -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

Recent he-basic-ansible-suite-4.2 failures
by Yedidyah Bar David 02 Jul '18

02 Jul '18

Hi all, I noticed that our hosted-engine suites [1] often fail recently, and decided to have a look at [2], which are on 4.2, which should hopefully be "rock solid" and basically never fail. I looked at these, [3][4][5][6][7], which are all the ones that still appear in [2] and marked as failed. Among them: - All but one failed while "Waiting for agent to be ready" and timing out after 10 minutes, as part of 008_restart_he_vm.py, which was added a month ago [8] and then patched [9]. - The other one [7] failed while "Waiting for engine to migrate", also eventually timing out after 10 minutes, as part of 010_local_mainentance.py, which was also added in [9]. I also had a look at the last ones that succeeded, builds 329 to 337 of [2]. There: - "Waiting for agent to be ready" took between 26 and 48 seconds - "Waiting for engine to migrate" took between 69 and 82 seconds Assuming these numbers are reasonable (which might be debatable), 10 minutes indeed sounds like a reasonable timeout, and I think we should handle each failure specifically. Did anyone check them? Was it an infra issue/load/etc.? A bug? Something else? I didn't check the logs yet, might do this later. Also didn't check the failures in other jobs in [1]. Best regards, [1] https://jenkins.ovirt.org/search/?q=he-basic [2] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2/ [3] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [4] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [5] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [6] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [7] https://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-ansible-suite-4.2… [8] https://gerrit.ovirt.org/91952 [9] https://gerrit.ovirt.org/92341 -- Didi

3 3