This was the original message:

Received-SPF: pass (google.com: domain of infra-bounces@ovirt.org designates 66.187.230.42 as permitted sender) client-ip=66.187.230.42;
Subject: [CQ]: 83732,5 (vdsm) failed "ovirt-master" system tests
To: infra@ovirt.org
From: oVirt Jenkins <jenkins@ovirt.org>
Message-Id: <20171110212700.BEC29C0A5632@vm0043.workers-phx.ovirt.org>
Date: Fri, 10 Nov 2017 21:27:00 +0000 (UTC)
Precedence: list
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: infra-bounces@ovirt.org
Errors-To: infra-bounces@ovirt.org

Change 83732,5 (vdsm) 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/83732/5

For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/3753/
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

On Sun, Nov 12, 2017 at 5:07 PM Barak Korren (oVirt JIRA) <jira@ovirt-jira.atlassian.net> wrote:

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=35330#comment-35330 ]
Barak Korren commented on OVIRT-1751:

[~nsoffer@redhat.com] There are multitude of messages that appear to be sent from Jenkins, and they are sent from different systems that are configured differently. Please quote the message you are referring to.
Please note that we do not regard email as a primary communication means between Jenkins and developers. Jenkins typically posts important information beck to the SCM systems, while email is typically meant for infra team scrutiny. This is why we are not likely to take responses to email that Jenkins sends seriously (E.g the typical repose would be, "we know, this email was meant for us, not you").
Re: Delivery Status Notification (Failure)
     Key: OVIRT-1751
     URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1751
 Project: oVirt - virtualization made easy
         Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
        Attachments: icon.png
Mail from jenkins@ovirt.org should use a reply-to header so replies go the proper mailing list (e.g. infra@ovirt.org), or if we don't have anything that make sense, noreply@ovirt.org? On Sat, Nov 11, 2017 at 2:02 AM Mail Delivery Subsystem < mailer-daemon@googlemail.com> wrote:

[image: icon.png] Address not found Your message wasn't delivered to jenkins@ovirt.org because the address couldn't be found. Check for typos or unnecessary spaces and try again. The response from the remote server was:

550 5.1.1 <jenkins@ovirt.org>: Recipient address rejected: User unknown in local recipient table

---------- Forwarded message ---------- From: Nir Soffer <nsoffer@redhat.com> To: oVirt Jenkins <jenkins@ovirt.org> Cc: infra@ovirt.org, Dan Kenigsberg <danken@redhat.com> Bcc: Date: Sat, 11 Nov 2017 00:02:32 +0000 Subject: Re: [CQ]: 83732,5 (vdsm) failed “ovirt-master” system tests This looks like lago issue, not related to the vdsm patch:

00:09:11.669 [basic-suit] * Running reposync: ERROR (in 0:03:00)*00:09:11.672* [basic-suit] # Syncing remote repos locally (this might take some time): ERROR (in 0:03:00)

<b style=

— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra