A system test invoked by the "ovirt-master" change queue including change
100368,2 (vdsm) failed. However, this change seems not to be the root cause for
this failure. Change 100312,2 (vdsm) 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 100312,2 (vdsm) 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/100368/2
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/100312/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14358/
Change 100302,2 (ovirt-wgt) 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/100302/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14354/
A system test invoked by the "ovirt-master" change queue including change
100092,6 (ovirt-engine) failed. However, this change seems not to be the root
cause for this failure. Change 100309,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 100309,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/100092/6
For further details about the change that seems to be the root cause behind the
testing failures see:
https://gerrit.ovirt.org/#/c/100309/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/14349/
Change 100377,2 (ovirt-engine-ui-extensions) is probably the reason behind
recent system test failures in the "ovirt-4.3" 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/100377/2
For failed test results see:
http://jenkins.ovirt.org/job/ovirt-4.3_change-queue-tester/1032/
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jir... ]
Ehud Yonasi commented on OVIRT-2736:
------------------------------------
It fails on installing createrepo package which probably does not exist in
fc30.
We are working on fixing it.
On Thu, May 30, 2019 at 4:05 PM Marcin Sobczyk <msobczyk(a)redhat.com> wrote:
> Hi,
> On 5/30/19 2:43 PM, Nir Soffer wrote:
>
>
> On Thu, May 30, 2019 at 3:41 PM Nir Soffer <nsoffer(a)redhat.com> wrote:
>
>> Here a failed build:
>>
>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
>>
>
> Marcin, can it be related to the latest py3 changes?
>
> Don't really think so - please notice that only s390x agents are touched.
> The only thing that changed recently was adding a 'build-artifacts' job
> that uses Python 3.6 to build artifacts on s390x machines.
> I've recently reported a problem that the agents ran out of space and it
> was fixed by Ehud:
>
> https://ovirt-jira.atlassian.net/browse/OVIRT-2734
>
> Ehud, did you notice anything weird occupying disk space on these agents?
>
>
>>
>> The second failure today.
>>
>> I hope we can fix this quickly.
>>
>> If not we need to disable fedora builds for now.
>>
>
> Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
> ----------------------------------------------------------------------------------------------
>
> Key: OVIRT-2736
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> Here a failed build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
> The second failure today.
> I hope we can fix this quickly.
> If not we need to disable fedora builds for now.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100103)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jir... ]
Marcin Sobczyk commented on OVIRT-2736:
---------------------------------------
Hi,
On 5/30/19 2:43 PM, Nir Soffer wrote:
>
> On Thu, May 30, 2019 at 3:41 PM Nir Soffer <nsoffer(a)redhat.com
> <mailto:nsoffer@redhat.com>> wrote:
>
> Here a failed build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
>
>
> Marcin, can it be related to the latest py3 changes?
Don't really think so - please notice that only s390x agents are touched.
The only thing that changed recently was adding a 'build-artifacts' job
that uses Python 3.6 to build artifacts on s390x machines.
I've recently reported a problem that the agents ran out of space and it
was fixed by Ehud:
https://ovirt-jira.atlassian.net/browse/OVIRT-2734
Ehud, did you notice anything weird occupying disk space on these agents?
>
>
> The second failure today.
>
> I hope we can fix this quickly.
>
> If not we need to disable fedora builds for now.
>
> Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
> ----------------------------------------------------------------------------------------------
>
> Key: OVIRT-2736
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> Here a failed build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
> The second failure today.
> I hope we can fix this quickly.
> If not we need to disable fedora builds for now.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100103)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2736?page=com.atlassian.jir... ]
Nir Soffer commented on OVIRT-2736:
-----------------------------------
On Thu, May 30, 2019 at 3:45 PM Barak Korren <bkorren(a)redhat.com> wrote:
> Please track issues on the ticket you already opened about this and avoid
> spreading the information over multiple threads.
>
> Its the s390x issue I already explained - its running f30 atm which is
> causing some trouble because the `createrepo` package was dropped from it.
>
Thanks, I did not notice this is again s390x, you can close this.
>
> On Thu, 30 May 2019 at 15:41, Nir Soffer <nsoffer(a)redhat.com> wrote:
>
>> Here a failed build:
>>
>> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
>>
>> The second failure today.
>>
>> I hope we can fix this quickly.
>>
>> If not we need to disable fedora builds for now.
>>
>
>
> --
> Barak Korren
> RHV DevOps team , RHCE, RHCi
> Red Hat EMEA
> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted
>
> Jenkins build artifacts fail on Fedora - global_setup[lago_setup] WARN: Lago directory missing
> ----------------------------------------------------------------------------------------------
>
> Key: OVIRT-2736
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2736
> Project: oVirt - virtualization made easy
> Issue Type: By-EMAIL
> Reporter: Nir Soffer
> Assignee: infra
>
> Here a failed build:
> https://jenkins.ovirt.org/blue/organizations/jenkins/standard-manual-runn...
> The second failure today.
> I hope we can fix this quickly.
> If not we need to disable fedora builds for now.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100103)