June 2018 - Infra - Ovirt List Archives

[CQ]: 92335, 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 92335,1 (ovirt-engine) failed. However, this change seems not to be the root cause for this failure. Change 92245,3 (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 92245,3 (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/92335/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/92245/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8268/

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2215) Developer permissions - Ovirt Jenkins

by Asaf Rachmani (oVirt JIRA)

Asaf Rachmani created OVIRT-2215: ------------------------------------ Summary: Developer permissions - Ovirt Jenkins Key: OVIRT-2215 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2215 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Asaf Rachmani Assignee: infra Hi, Can you please provide me developer permissions in Ovirt Jenkins (re-trigger option for example)? Thanks, Asaf -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves

by Evgheni Dereveanchin (oVirt JIRA)

Evgheni Dereveanchin created OVIRT-2214: ------------------------------------------- Summary: proxy test fails due to wget missing on CI slaves Key: OVIRT-2214 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2214 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra A lot of jobs have this warning in their logs: Failed to contact proxy http://proxy01.phx.ovirt.org:3128, falling back to non-proxied config The proxy is running fine and is reachable yet wget is missing in minimal setups of CentOS and Fedora. We are not installing it from global_setup and it seems to be needed by the try_proxy function of mock_runner that is used to generate mock configs. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jir... ] Daniel Belenky reassigned OVIRT-1717: ------------------------------------- Assignee: Daniel Belenky (was: infra) > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: Daniel Belenky > Labels: change-queue, standard-ci > > As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. > *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying > {code:java} > tag-on-release: > enabled: True > tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" > {code} > "standard stage" will add the relevant information to the change object and CQ will handle the tagging. > Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash

by Daniel Belenky (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jir... ] Daniel Belenky updated OVIRT-1717: ---------------------------------- Description: As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying {code:java} tag-on-release: enabled: True tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" {code} "standard stage" will add the relevant information to the change object and CQ will handle the tagging. Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) was:Tagging the source git would make it easier for me to tell if a specific git commit is already tested by OST and available for QA. > When a component build passes OST, tag its git hash > --------------------------------------------------- > > Key: OVIRT-1717 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1717 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Change Queue > Reporter: danken > Assignee: infra > Labels: change-queue, standard-ci > > As a project maintainer, I want to see which changes passed CI gating (aka CQ) so that it will be easy for me to tell if a specific commit was tested in CQ and is available for QA. > *Scenario:* Project maintainer specifies in _stdci.yaml_ config that he wants STDCI to tag changes of this project by specifying > {code:java} > tag-on-release: > enabled: True > tag_template: "SomeTemplate with Jinja support { branch } and { queue_name } variables should be available too" > {code} > "standard stage" will add the relevant information to the change object and CQ will handle the tagging. > Need to see if the tags will be pushed by CQ as well or another component should be used (such as pusher.py) -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jir... ] Barak Korren commented on OVIRT-2201: ------------------------------------- [~sbonazzo(a)redhat.com] I'll need some help to write the user stories for the requirements you state so we can properly evaluate and triage them. {quote} a way to quickly see if jobs are failing on a specific branch {quote} How about: "As an oVirt developer, I want to see the build status for the HEAD commit of a particular branch of my project so that I can <need to fill in reason here>" {quote} a way to consume builds from a specific branch {quote} "As an oVirt developer I want to have a way to acquire the lasted CI build on a particular branch on a particular project so that I can use it as a dependency for other jobs". About this last one - I guess we can ask people in devel if "tested" would be a good enough compromise? > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBu... > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years, 7 months

1
0
0 / 0

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests

by oVirt Jenkins

Change 92278,1 (ovirt-appliance) 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/92278/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8264/

6 years, 7 months

2
1
0 / 0

[CQ]: 92278,1 (ovirt-appliance) failed "ovirt-master" system tests

by oVirt Jenkins

Change 92278,1 (ovirt-appliance) 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/92278/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8262/

6 years, 7 months

2
1
0 / 0

[CQ]: 92323,2 (ovirt-engine) failed "ovirt-4.2" system tests

by oVirt Jenkins

Change 92323,2 (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/92323/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2431/

6 years, 7 months

1
0
0 / 0

[CQ]: 92245,3 (ovirt-engine) failed "ovirt-master" system tests

by oVirt Jenkins

Change 92245,3 (ovirt-engine) 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/92245/3 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8258/

6 years, 7 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018