- Infra - oVirt List Archives

[CQ]: 91733, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

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

1 0

[JIRA] (OVIRT-2072) build-artifacts job failed to fetch git with returned status code 143
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2072?page=com.atlassian.jira.… ] Dafna Ron updated OVIRT-2072: ----------------------------- Labels: cq-issue-traking ost_failures ost_infra (was: ost_failures ost_infra) > build-artifacts job failed to fetch git with returned status code 143 > --------------------------------------------------------------------- > > Key: OVIRT-2072 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2072 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: cq-issue-traking, ost_failures, ost_infra > > put vm offline (could not see a host in log) and re-ran the artifacts job. > Change 91568,10 (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/91568/10 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/ > 08:50:28 > git init /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-fc27-x86_64/ovirt-provider-ovn # timeout=10 > 08:50:28 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-provider-ovn.git > 08:50:28 > git --version # timeout=10 > 08:50:28 > git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/* > 09:00:28 ERROR: Timeout after 10 minutes > 09:00:28 ERROR: Error cloning remote repo 'origin' > 09:00:28 hudson.plugins.git.GitException: Command "git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/*" returned status code 143: > 09:00:28 stdout: > 09:00:28 stderr: remote: Counting objects: 84340 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

post-merge CI triggering from GitHub
by Barak Korren 31 May '18

31 May '18

Its broken right now, we're investigating the issue. Tracker ticket: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 Thanks Tomas Golembiovsky for reporting! -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted

1 1

[CQ]: 91732, 1 (ovirt-engine) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 31 May '18

31 May '18

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

2 1

[CQ]: 72008, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 72008,1 (ovirt-engine-extension-aaa-misc) 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/72008/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7997/

1 0

[JIRA] (OVIRT-2072) build-artifacts job failed to fetch git with returned status code 143
by Dafna Ron (oVirt JIRA) 31 May '18

31 May '18

Dafna Ron created OVIRT-2072: -------------------------------- Summary: build-artifacts job failed to fetch git with returned status code 143 Key: OVIRT-2072 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2072 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra put vm offline (could not see a host in log) and re-ran the artifacts job. Change 91568,10 (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/91568/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/ 08:50:28 > git init /home/jenkins/workspace/ovirt-provider-ovn_master_build-artifacts-fc27-x86_64/ovirt-provider-ovn # timeout=10 08:50:28 Fetching upstream changes from git://gerrit.ovirt.org/ovirt-provider-ovn.git 08:50:28 > git --version # timeout=10 08:50:28 > git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/* 09:00:28 ERROR: Timeout after 10 minutes 09:00:28 ERROR: Error cloning remote repo 'origin' 09:00:28 hudson.plugins.git.GitException: Command "git fetch --tags --progress git://gerrit.ovirt.org/ovirt-provider-ovn.git +refs/heads/*:refs/remotes/origin/*" returned status code 143: 09:00:28 stdout: 09:00:28 stderr: remote: Counting objects: 84340 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[CQ]: 91568, 10 (ovirt-provider-ovn) failed "ovirt-master" system tests
by oVirt Jenkins 31 May '18

31 May '18

Change 91568,10 (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/91568/10 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7993/

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2071?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2071: ----------------------------------- Assignee: Barak Korren (was: infra) > post-merge triggering from GitHub Isn't working (again) > ------------------------------------------------------- > > Key: OVIRT-2071 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: GitHub, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: Barak Korren > > Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

Barak Korren created OVIRT-2071: ----------------------------------- Summary: post-merge triggering from GitHub Isn't working (again) Key: OVIRT-2071 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 Project: oVirt - virtualization made easy Issue Type: Outage Components: GitHub, Standard CI (Pipelines) Reporter: Barak Korren Assignee: infra Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0

[JIRA] (OVIRT-2071) post-merge triggering from GitHub Isn't working (again)
by Barak Korren (oVirt JIRA) 31 May '18

31 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2071?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2071: -------------------------------- Epic Link: OVIRT-400 > post-merge triggering from GitHub Isn't working (again) > ------------------------------------------------------- > > Key: OVIRT-2071 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2071 > Project: oVirt - virtualization made easy > Issue Type: Outage > Components: GitHub, Standard CI (Pipelines) > Reporter: Barak Korren > Assignee: infra > > Post merge events fro github are triggering (via webhooks) the 'standard-webhook-trigger' job but for some reason jenkins is no longer passing the information from the GitHub webhook to it , so the job cannot trigger the proper STDCI job to handle the merge event. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100086)

1 0