- Infra - oVirt List Archives

[JIRA] (OVIRT-2265) ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number:
by Dafna Ron (oVirt JIRA) 28 Jun '18

28 Jun '18

Dafna Ron created OVIRT-2265: -------------------------------- Summary: ovirt-engine cq failing on test 098_ovirt_provider_ovn.use_ovn_provider - libvirtError: 'queues' attribute must be positive number: Key: OVIRT-2265 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2265 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Priority: Highest The change reported as responsible for the failure was a package change patch but I can see that some patches merged by Alona are more related to the issue. mail sent to list. Although CQ is pointing to this change: https://gerrit.ovirt.org/#/c/92567/ - packaging: Add python-netaddr requirement I actually think from the error its because of changes made to multiqueues https://gerrit.ovirt.org/#/c/92009/ - engine: Update libvirtVmXml to consider vmBase.multiQueuesEnabled attribute https://gerrit.ovirt.org/#/c/92008/ - engine: Introduce algorithm for calculating how many queues asign per vnic https://gerrit.ovirt.org/#/c/92007/ - engine: Add multiQueuesEnabled to VmBase https://gerrit.ovirt.org/#/c/92318/ - restapi: Add 'Multi Queues Enabled' to the relevant mappers https://gerrit.ovirt.org/#/c/92149/ - webadmin: Add 'Multi Queues Enabled' to vm dialog Link to Job: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8375/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 91784, 3 (ovirt-hosted-engine-ha) failed "ovirt-master" system tests
by oVirt Jenkins 28 Jun '18

28 Jun '18

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

1 0

[JIRA] (OVIRT-2259) fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported"
by Piotr Kliczewski (oVirt JIRA) 28 Jun '18

28 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Piotr Kliczewski commented on OVIRT-2259: ----------------------------------------- This could be related to jdk [bug|https://bugs.openjdk.java.net/browse/JDK-8182580] > fc28: Failed to add ovirt-host: "The key algorithm 'EC' is not supported" > ------------------------------------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > Attachments: host-0-journal.txt > > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Dafna Ron (oVirt JIRA) 28 Jun '18

28 Jun '18

Dafna Ron created OVIRT-2264: -------------------------------- Summary: Cannot deactivate Storage while there are running tasks on this Storage Key: OVIRT-2264 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2264 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra we failed test: 007_sd_reattach.deactivate_storage_domain in vdsm project with error: Cannot deactivate Storage while there are running tasks on this Storage. -Please wait until tasks will finish and try again.]". HTTP response code is 409. I am opening this as a race in case something changed in OST tests which would cause this to repeat. https://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2506 https://gerrit.ovirt.org/#/c/92313/2 -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2175) Move oVirt projects to STDCI V2
by Daniel Belenky (oVirt JIRA) 27 Jun '18

27 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2175?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2175: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Move oVirt projects to STDCI V2 > ------------------------------- > > Key: OVIRT-2175 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2175 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: oVirt CI > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > As STDCI V2 is live and production for a while now, it's time to proactively push and assist oVirt projects to move to STDCI V2. Projects will benefit from new STDCI V2 features such as the ability to modify the distributions and architectures they build on without having to send patches to the 'Jenkins' repo. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

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

27 Jun '18

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

1 0

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

27 Jun '18

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

1 0

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

27 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: 283 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #283 [Gal Ben Haim] Make sure that crond is installed and running [Barak Korren] Install JJB via PIP instead of YUM [Barak Korren] Clean deprecation warning from JJB output [Barak Korren] Upgrade JJB to 1.6.2 ----------------- Failed Tests: ----------------- All tests passed

1 1

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

27 Jun '18

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

1 0

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

27 Jun '18

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

1 0