October 2019 - Infra - oVirt List Archives

[CQ]: 103014, 7 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Oct '19

01 Oct '19

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

1 0

[CQ]: 103704, 1 (ovirt-engine) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Oct '19

01 Oct '19

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

1 0

[CQ]: 103683, 1 (ovirt-host) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Oct '19

01 Oct '19

A system test invoked by the "ovirt-master" change queue including change 103683,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/103683/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/16165/

1 0

[JIRA] (OVIRT-2806) Java 8 to 11 migration for vdsm-jsonrpc-java job
by Artur Socha (oVirt JIRA) 01 Oct '19

01 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2806?page=com.atlassian.jira.… ] Artur Socha updated OVIRT-2806: ------------------------------- Resolution: Won't Do Status: Done (was: To Do) Closing because I actually have learned how/where the jobs are configured > Java 8 to 11 migration for vdsm-jsonrpc-java job > ------------------------------------------------ > > Key: OVIRT-2806 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2806 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: CI client projects, Jenkins Slaves > Reporter: Artur Socha > Assignee: infra > Priority: Low > > vdsm-jsonrpc-java is supposed to be built using OpenJDK 11.0.4. > https://jenkins.ovirt.org/view/Master%20branch%20per%20project/view/vdsm-js… > Jenkins job seems to be still using JDK 1.8. Could you please help with changing its configuration to use JDK 11 by default or advise me whether I can do it by myself? > I believe ovirt-engine job can be used as reference as it is already running builds with JDK 11. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 103705, 1 (ovirt-hosted-engine-setup) failed "ovirt-master" system tests, but isn't the failure root cause
by oVirt Jenkins 01 Oct '19

01 Oct '19

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

1 0

Unable to Upgrade
by Akshita Jain 01 Oct '19

01 Oct '19

After upgrading oVirt 4.3.4 to 4.3.6, the gluster is also upgrading from 5.6 to 6.5. But as soon as it upgrades gluster peer status shows disconnected. What is the correct method to upgrade oVirt with gluster HCI environment?

1 0

[JIRA] (OVIRT-2806) Java 8 to 11 migration for vdsm-jsonrpc-java job
by Artur Socha (oVirt JIRA) 01 Oct '19

01 Oct '19

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2806?page=com.atlassian.jira.… ] Artur Socha updated OVIRT-2806: ------------------------------- Summary: Java 8 to 11 migration for vdsm-jsonrpc-java job (was: Java 8 to 11 migration for vdsm-jsonrpci-java job) > Java 8 to 11 migration for vdsm-jsonrpc-java job > ------------------------------------------------ > > Key: OVIRT-2806 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2806 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: CI client projects, Jenkins Slaves > Reporter: Artur Socha > Assignee: infra > Priority: Low > > vdsm-jsonrpc-java is supposed to be built using OpenJDK 11.0.4. > https://jenkins.ovirt.org/view/Master%20branch%20per%20project/view/vdsm-js… > Jenkins job seems to be still using JDK 1.8. Could you please help with changing its configuration to use JDK 11 by default or advise me whether I can do it by myself? > I believe ovirt-engine job can be used as reference as it is already running builds with JDK 11. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: 103708,2 (jenkins) failed "dummy-master" system tests
by oVirt Jenkins 01 Oct '19

01 Oct '19

Change 103708,2 (jenkins) is probably the reason behind recent system test failures in the "dummy-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/103708/2 For failed test results see: https://jenkins-staging.ovirt.org/job/dummy-master_change-queue-tester/306/

1 0

[JIRA] (OVIRT-2806) Java 8 to 11 migration for vdsm-jsonrpci-java job
by Artur Socha (oVirt JIRA) 01 Oct '19

01 Oct '19

Artur Socha created OVIRT-2806: ---------------------------------- Summary: Java 8 to 11 migration for vdsm-jsonrpci-java job Key: OVIRT-2806 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2806 Project: oVirt - virtualization made easy Issue Type: Task Components: CI client projects, Jenkins Slaves Reporter: Artur Socha Assignee: infra Priority: Low vdsm-jsonrpc-java is supposed to be built using OpenJDK 11.0.4. https://jenkins.ovirt.org/view/Master%20branch%20per%20project/view/vdsm-js… Jenkins job seems to be still using JDK 1.8. Could you please help with changing its configuration to use JDK 11 by default or advise me whether I can do it by myself? I believe ovirt-engine job can be used as reference as it is already running builds with JDK 11. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100111)

1 0

[CQ]: eb70453 (ovirt-ansible-engine-setup) failed "ovirt-master" system tests
by oVirt Jenkins 01 Oct '19

01 Oct '19

Change eb70453 (ovirt-ansible-engine-setup) 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://github.com/oVirt/ovirt-ansible-engine-setup/commit/eb704538e47c4c3e… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/16157/

1 0