September 2019 - Infra - Ovirt List Archives

[JIRA] (OVIRT-2764) send email on changequeue-status_master_standard-poll-upstream-sources failure

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2764?page=com.atlassian.jir... ] Eyal Edri commented on OVIRT-2764: ---------------------------------- [~accountid:5aa0f39f5a4d022884128a0f] can you verify this is done? > send email on changequeue-status_master_standard-poll-upstream-sources failure > ------------------------------------------------------------------------------ > > Key: OVIRT-2764 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2764 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins Master > Reporter: danken > Assignee: infra > > OVIRT-2755 has enabled the new periodic job. I'd like to receive an email when it fails. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2782) Configure Jenkins to wait less and allocate more

by Eyal Edri (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2782?page=com.atlassian.jir... ] Eyal Edri reassigned OVIRT-2782: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Configure Jenkins to wait less and allocate more > ------------------------------------------------ > > Key: OVIRT-2782 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2782 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Daniel Belenky > Assignee: Evgheni Dereveanchin > > By default, Jenkins is configured to wait a few seconds before allocating a new node in a hope that a node in use to be freed. We can control this setting by setting > {code:java} > hudson.slaves.NodeProvisioner.initialDelay=0 > {code} > We can also control the excessive workload threshold and force Jenkins to allocate slaves for jobs in the queue... but, because Jenkins computes the excess workload value (which decides if we need to allocate a new node) using an EMA, we set it's margins to higher values and it effectively lowers its threshold so that Jenkins will allocate nodes faster and in advance. > The recommended settings by the k8s plugin to spawn a node for every build in the queue: > {code:java} > -Dhudson.slaves.NodeProvisioner.initialDelay=0 > -Dhudson.slaves.NodeProvisioner.MARGIN=50 > -Dhudson.slaves.NodeProvisioner.MARGIN0=0.85 > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 4 months

1
0
0 / 0

[CQ]: 103009, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years, 4 months

1
0
0 / 0

[CQ]: 103006, 2 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2786: ---------------------------------- I am surprised it did not comment on the bug as it usually does and it also sends a mail to the list. However, I think as we are going to work with zuul, it may not be effective to work on CQ :) > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 4 months

1
0
0 / 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

by Dafna Ron (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2786?page=com.atlassian.jir... ] Dafna Ron commented on OVIRT-2786: ---------------------------------- packages only get into tested once they pass CQ. I looked at the latest patch that that build packages and it failed CQ: patch: [https://gerrit.ovirt.org/#/c/102941/|https://gerrit.ovirt.org/#/c/102941/] job [http://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-master_change-queue-tester/15617/|http://jenkins.ovirt.org...] > Re: fc30 packages in master snapshot > ------------------------------------ > > Key: OVIRT-2786 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Anton Marchukov > Assignee: infra > > Adding infra-support to open a ticket. > > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > > > Hi, > > > > How are these published? > > > > A few days ago we merged patches to add fc30 builds of otopi and > > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > > good. But we do not see them in [1]. Should we? Are they stuck > > somewhere, or there is simply nothing that publishes them these days? > > Asking the latter, because the timestamps on the few files there are > > from more than 3 months ago. > > > > Thanks and best regards, > > > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > > -- > > Didi > -- > Anton Marchukov > Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 4 months

3
2
0 / 0

[JIRA] (OVIRT-2786) Re: fc30 packages in master snapshot

by Anton Marchukov (oVirt JIRA)

Anton Marchukov created OVIRT-2786: -------------------------------------- Summary: Re: fc30 packages in master snapshot Key: OVIRT-2786 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2786 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Anton Marchukov Assignee: infra Adding infra-support to open a ticket. > On 2 Sep 2019, at 09:09, Yedidyah Bar David <didi(a)redhat.com> wrote: > > Hi, > > How are these published? > > A few days ago we merged patches to add fc30 builds of otopi and > ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems > good. But we do not see them in [1]. Should we? Are they stuck > somewhere, or there is simply nothing that publishes them these days? > Asking the latter, because the timestamps on the few files there are > from more than 3 months ago. > > Thanks and best regards, > > [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ > -- > Didi -- Anton Marchukov Associate Manager - RHV DevOps - Red Hat -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100108)

5 years, 4 months

1
0
0 / 0

fc30 packages in master snapshot

by Yedidyah Bar David

Hi, How are these published? A few days ago we merged patches to add fc30 builds of otopi and ovirt-host-deploy. Jenkins ran build-artifacts on them and all seems good. But we do not see them in [1]. Should we? Are they stuck somewhere, or there is simply nothing that publishes them these days? Asking the latter, because the timestamps on the few files there are from more than 3 months ago. Thanks and best regards, [1] https://resources.ovirt.org/pub/ovirt-master-snapshot-static/rpm/fc30/ -- Didi

5 years, 4 months

1
0
0 / 0

oVirt infra daily report - unstable production jobs - 935

by jenkins＠jenkins.phx.ovirt.org

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/935//artifact/exported... Cheers, Jenkins

5 years, 4 months

1
0
0 / 0

[CQ]: 103002, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause

by oVirt Jenkins

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

5 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra September 2019