November 2017 - Infra - oVirt List Archives

[CQ]: 83508, 2 (ovirt-engine) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

[JIRA] (OVIRT-1733) cleanup deploy-ovirt-experimental leftovers from resources
by Evgheni Dereveanchin (oVirt JIRA) 02 Nov '17

02 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1733?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1733: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > cleanup deploy-ovirt-experimental leftovers from resources > ---------------------------------------------------------- > > Key: OVIRT-1733 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1733 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > While working on OVIRT-1721 today I noticed that the resources file server still has a deploy-ovirt-experimental user that has active cron tasks running periodically. As experimental does not exist, this should be removed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[CQ]: 83492, 2 (ovirt-engine) failed "ovirt-4.1" system tests, but isn't the failure root cause
by oVirt Jenkins 02 Nov '17

02 Nov '17

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

1 0

oVirt infra weekly meeting notes 01.11.2017
by Evgheni Dereveanchin 02 Nov '17

02 Nov '17

Hi everyone, please find the topics of today's infra meeting below: - Staging Engine still has Gluster issues OVIRT-1121 <https://ovirt-jira.atlassian.net/browse/OVIRT-1121> - Ticket created to automate staging Engine auto-updates to Master OVIRT-1729 <https://ovirt-jira.atlassian.net/browse/OVIRT-1729> - VMs created on staging Engine and added to staging Jenkins - New guest VLAN configured properly, named external-phx.ovirt.org - New lago issue causing shell processes to get left over OVIRT-1730 <https://ovirt-jira.atlassian.net/browse/OVIRT-1730> -- Regards, Evgheni Dereveanchin

2 1

Jenkins build became unstable: ovirt_4.1_publish-rpms_nightly #361
by jenkins＠jenkins.phx.ovirt.org 02 Nov '17

02 Nov '17

See <http://jenkins.ovirt.org/job/ovirt_4.1_publish-rpms_nightly/361/display/red…>

1 1

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 02 Nov '17

02 Nov '17

Barak Korren created OVIRT-1734: ----------------------------------- Summary: Add CI jobs to test slaves on staging engine Key: OVIRT-1734 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 Project: oVirt - virtualization made easy Issue Type: New Feature Components: oVirt CI, oVirt Infra Reporter: Barak Korren Assignee: infra After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

[JIRA] (OVIRT-1734) Add CI jobs to test slaves on staging engine
by Barak Korren (oVirt JIRA) 02 Nov '17

02 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1734?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1734: -------------------------------- Epic Link: OVIRT-400 > Add CI jobs to test slaves on staging engine > -------------------------------------------- > > Key: OVIRT-1734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1734 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: oVirt CI, oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: staging > > After the staging engine was installed, several VMs were created on it and added as slaves to the staging Jenkins. > We need to add some jobs that will take advantage on those slaves so we can tell if they are working properly. > The should probably just add CI jobs for the 'jenkins' repo. That repo is already configured to run some jobs on the staging Jenkins and is mostly maintained by our team, so and issues there will be visible to us. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

Jenkins build became unstable: ovirt_4.2_publish-rpms_nightly #9
by jenkins＠jenkins.phx.ovirt.org 02 Nov '17

02 Nov '17

See <http://jenkins.ovirt.org/job/ovirt_4.2_publish-rpms_nightly/9/display/redir…>

1 1

[JIRA] (OVIRT-1733) cleanup deploy-ovirt-experimental leftovers from resources
by Barak Korren (oVirt JIRA) 02 Nov '17

02 Nov '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1733?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1733: ------------------------------------- The user is still needed, it is used for deploying to 'tested' as well. The cron tasks are probably not needed any more. > cleanup deploy-ovirt-experimental leftovers from resources > ---------------------------------------------------------- > > Key: OVIRT-1733 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1733 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: infra > > While working on OVIRT-1721 today I noticed that the resources file server still has a deploy-ovirt-experimental user that has active cron tasks running periodically. As experimental does not exist, this should be removed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100070)

1 0

Jenkins build became unstable: ovirt_master_publish-rpms_nightly #752
by jenkins＠jenkins.phx.ovirt.org 02 Nov '17

02 Nov '17

See <http://jenkins.ovirt.org/job/ovirt_master_publish-rpms_nightly/752/display/…>

1 2