- Infra - oVirt List Archives

[JIRA] (OVIRT-1370) deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job
by Barak Korren (oVirt JIRA) 09 May '17

09 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1370?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1370: ----------------------------------- Assignee: Barak Korren (was: infra) > deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job > ---------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1370 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1370 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > When project build to a version of oVirt that does not have an OST job the 'deploy-to-experimental' job fails because it tries to run an experimental test job that does not exist. Once it fails, it also does not run the experimental jobs that do exist if the project is supposed to deploy to them too. > The solution to this should be: > # Catch the exception for failing to build a non-existent job so that other jobs would be launched. > # Change the error message reported to Gerrit in this case to explain the developers that they need to stop building to oVirt versions without experimental flows. > Example run that failed on this issue: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/948/ -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[JIRA] (OVIRT-1370) deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job
by Barak Korren (oVirt JIRA) 09 May '17

09 May '17

Barak Korren created OVIRT-1370: ----------------------------------- Summary: deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job Key: OVIRT-1370 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1370 Project: oVirt - virtualization made easy Issue Type: Bug Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: High When project build to a version of oVirt that does not have an OST job the 'deploy-to-experimental' job fails because it tries to run an experimental test job that does not exist. Once it fails, it also does not run the experimental jobs that do exist if the project is supposed to deploy to them too. The solution to this should be: # Catch the exception for failing to build a non-existent job so that other jobs would be launched. # Change the error message reported to Gerrit in this case to explain the developers that they need to stop building to oVirt versions without experimental flows. Example run that failed on this issue: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/948/ -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[JIRA] (OVIRT-1370) deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job
by Barak Korren (oVirt JIRA) 09 May '17

09 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1370?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1370: -------------------------------- Epic Link: OVIRT-400 > deploy-to-experimental job fails when project builds to a version of oVirt that does not have an experimental test job > ---------------------------------------------------------------------------------------------------------------------- > > Key: OVIRT-1370 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1370 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: High > > When project build to a version of oVirt that does not have an OST job the 'deploy-to-experimental' job fails because it tries to run an experimental test job that does not exist. Once it fails, it also does not run the experimental jobs that do exist if the project is supposed to deploy to them too. > The solution to this should be: > # Catch the exception for failing to build a non-existent job so that other jobs would be launched. > # Change the error message reported to Gerrit in this case to explain the developers that they need to stop building to oVirt versions without experimental flows. > Example run that failed on this issue: > http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/948/ -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #947 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 May '17

09 May '17

------=_Part_102_1985321021.1494337529574 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/947/ Build Name: 947 ovirt-scheduler-proxy (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76507 - title: Change automation repositiries for el6 and fc22 - project: ovirt-scheduler-proxy - branch: master - author: Andrej Krejcir <akrejcir(a)redhat.com> ------=_Part_102_1985321021.1494337529574--

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #948 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 May '17

09 May '17

------=_Part_98_282442433.1494337266215 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/948/ Build Name: 948 ovirt-scheduler-proxy (3.6, 4.0, 4.1, master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76500 - title: Fix timeout and forced stop of scheduler methods - project: ovirt-scheduler-proxy - branch: master - author: Andrej Krejcir <akrejcir(a)redhat.com> ------=_Part_98_282442433.1494337266215--

1 1

[JIRA] (OVIRT-1369) PHX engine crashed unexpectedly 09.05.2017
by Evgheni Dereveanchin (oVirt JIRA) 09 May '17

09 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1369?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1369: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > PHX engine crashed unexpectedly 09.05.2017 > ------------------------------------------ > > Key: OVIRT-1369 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1369 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: Low > > I was managing VMs on the PHX Engine when it crashed unexpectedly around 13:30 GMT+1 time. It came up by iteslf after a few minutes so HA worked as expected, yet need to confirm what caused the crash as the Engine was updated to 4.1.1 recently. -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[JIRA] (OVIRT-1369) PHX engine crashed unexpectedly 09.05.2017
by Evgheni Dereveanchin (oVirt JIRA) 09 May '17

09 May '17

Evgheni Dereveanchin created OVIRT-1369: ------------------------------------------- Summary: PHX engine crashed unexpectedly 09.05.2017 Key: OVIRT-1369 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1369 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low I was managing VMs on the PHX Engine when it crashed unexpectedly around 13:30 GMT+1 time. It came up by iteslf after a few minutes so HA worked as expected, yet need to confirm what caused the crash as the Engine was updated to 4.1.1 recently. -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[oVirt Jenkins] deploy-to-ovirt_experimental - Build #918 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 May '17

09 May '17

------=_Part_82_1986270819.1494328410881 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/deploy-to-ovirt_experimental/918/ Build Name: 918 ovirt-vdsmfake (master) Build Status: FAILURE Gerrit change: https://gerrit.ovirt.org/76548 - title: cdi: utils injection. - project: ovirt-vdsmfake - branch: master - author: Eldad Marciano <emarcian(a)redhat.com> ------=_Part_82_1986270819.1494328410881--

1 0

[JIRA] (OVIRT-1368) http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/23419/
by Barak Korren (oVirt JIRA) 09 May '17

09 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1368?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1368: ----------------------------------- Assignee: Barak Korren (was: infra) > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/234… > ------------------------------------------------------------------------------ > > Key: OVIRT-1368 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1368 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: Barak Korren > > Hi, > Could someone help me to understand what has failed in ${subject} build? > Thanks in advance, > Yevgeny -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0

[JIRA] (OVIRT-1368) http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/23419/
by Barak Korren (oVirt JIRA) 09 May '17

09 May '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1368?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1368: ------------------------------------- This is probably cause by OVIRT-1086 [~yzaspits(a)redhat.com] let me know is re-triggering solves it, as it should. > http://jenkins.ovirt.org/job/ovirt-engine_master_check-patch-el7-x86_64/234… > ------------------------------------------------------------------------------ > > Key: OVIRT-1368 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1368 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yevgeny Zaspitsky > Assignee: infra > > Hi, > Could someone help me to understand what has failed in ${subject} build? > Thanks in advance, > Yevgeny -- This message was sent by Atlassian JIRA (v1000.929.2#100040)

1 0