- Infra - oVirt List Archives

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-master - Build # 256 - Failure!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-master… Build Number: 256 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #256 [Yedidyah Bar David] UI sanity: Increase timeout [Sandro Bonazzola] ovirt-jboss-modules-maven-plugin: move to v2 ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt CI] standard-enqueue - Build #14428 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 Jun '18

19 Jun '18

Build: http://jenkins.ovirt.org/job/standard-enqueue/14428/ Build Name: #14428 Build Description: Gerrit: 92316 - ovirt-imageio (4.2, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/92316 - title: docs: unix-support - project: ovirt-imageio - branch: master - author: Daniel Erez <derez(a)redhat.com>

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 272 - Failure!
by jenkins＠jenkins.phx.ovirt.org 18 Jun '18

18 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/272/ Build Number: 272 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #272 [Milan Zamazal] Make sure complete SS_PATH exists [Barak Korren] Control slave repos for FC28 [Barak Korren] Update slave mirror snapshots ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64
by eyal edri (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2216?page=com.atlassian.jira.… ] eyal edri commented on OVIRT-2216: ---------------------------------- This looks like a broken repo issue. Try closing 4.2 to external repos like we did for master. On Mon, Jun 18, 2018, 19:07 Dafna Ron (oVirt JIRA) < > Cannot find a valid baseurl for repo: base/7/x86_64 > --------------------------------------------------- > > Key: OVIRT-2216 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2216 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > vm deployment in lago fails with: > Cannot find a valid baseurl for repo: base/7/x86_64 > This is the 3ed time I have seen this and I think we may have network lag that is causing a time out. > [~ederevea] can you please take a look? > https://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-4.2_change-queue-tester/2431 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2216) Cannot find a valid baseurl for repo: base/7/x86_64
by Dafna Ron (oVirt JIRA) 18 Jun '18

18 Jun '18

Dafna Ron created OVIRT-2216: -------------------------------- Summary: Cannot find a valid baseurl for repo: base/7/x86_64 Key: OVIRT-2216 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2216 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra vm deployment in lago fails with: Cannot find a valid baseurl for repo: base/7/x86_64 This is the 3ed time I have seen this and I think we may have network lag that is causing a time out. [~ederevea] can you please take a look? https://jenkins.ovirt.org/view/Change queue jobs/job/ovirt-4.2_change-queue-tester/2431 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

2 1

[CQ]: 92335, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 18 Jun '18

18 Jun '18

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/

1 0

[JIRA] (OVIRT-2215) Developer permissions - Ovirt Jenkins
by Asaf Rachmani (oVirt JIRA) 18 Jun '18

18 Jun '18

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)

1 0

[JIRA] (OVIRT-2214) proxy test fails due to wget missing on CI slaves
by Evgheni Dereveanchin (oVirt JIRA) 18 Jun '18

18 Jun '18

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)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Daniel Belenky (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] 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)

1 0

[JIRA] (OVIRT-1717) When a component build passes OST, tag its git hash
by Daniel Belenky (oVirt JIRA) 18 Jun '18

18 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1717?page=com.atlassian.jira.… ] 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)

1 0