- Infra - oVirt List Archives

[JIRA] (OVIRT-2309) Update Gerrit infra-docs how to add STDCI V2 jobs
by Daniel Belenky (oVirt JIRA) 11 Jul '18

11 Jul '18

Daniel Belenky created OVIRT-2309: ------------------------------------- Summary: Update Gerrit infra-docs how to add STDCI V2 jobs Key: OVIRT-2309 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2309 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra As an STDCI user, I want to see clear documentation about adding new projects to STDCI so that I can setup STDCI for my project. Currently, the Gerrit documentation explains how to setup STDCI V1 only. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2308) ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1
by Dafna Ron (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2308?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2308: ---------------------------------- patch was merged accidentally. the revert is: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/00bb0c12dfa… I will close once I see project passing > ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1 > ---------------------------------------------------------------------------- > > Key: OVIRT-2308 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2308 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_code_regression, ost_failures, ost_packages > > Project failed: ovirt-ansible-disaster-recovery > branch failed: 4.2 and master > patch 4.2: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/4217ba1b6e4… > patch master: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/4217ba1b6e4… > build 4.2: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2620/ > build master: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8642/ > the issue is ansible package version: > ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1 > we currently take the package from https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.2/common/ and the latest package there is ansible-doc-2.5.5-1.el7.noarch.rpm -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 4217ba1 (ovirt-ansible-disaster-recovery) failed "ovirt-master" system tests
by oVirt Jenkins 11 Jul '18

11 Jul '18

Change 4217ba1 (ovirt-ansible-disaster-recovery) 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-disaster-recovery/commit/4217ba1b6e4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8642/

2 1

[JIRA] (OVIRT-2308) ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1
by Dafna Ron (oVirt JIRA) 11 Jul '18

11 Jul '18

Dafna Ron created OVIRT-2308: -------------------------------- Summary: ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1 Key: OVIRT-2308 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2308 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra Project failed: ovirt-ansible-disaster-recovery branch failed: 4.2 and master patch 4.2: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/4217ba1b6e4… patch master: https://github.com/oVirt/ovirt-ansible-disaster-recovery/commit/4217ba1b6e4… build 4.2: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2620/ build master: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8642/ the issue is ansible package version: ovirt-ansible-disaster-recovery-1.1.0-1.el7.noarch requires ansible >= 2.6.1 we currently take the package from https://buildlogs.centos.org/centos/7/virt/x86_64/ovirt-4.2/common/ and the latest package there is ansible-doc-2.5.5-1.el7.noarch.rpm -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2307) JJB jobs cannot properly use SSL
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2307?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-2307: ----------------------------------- Assignee: Barak Korren (was: infra) > JJB jobs cannot properly use SSL > -------------------------------- > > Key: OVIRT-2307 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2307 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: JJB > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > Our JJB jobs cannot properly use SSL ATM because the way we install JJB (inside a Python virtualenv with on system packages) makes the requests library it uses for HTTP to not know how to find the trusted CAs bundle file. > The way to solve this is to set the following variable in the JJB environment: > {code} > export REQUESTS_CA_BUNDLE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem > {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2307) JJB jobs cannot properly use SSL
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

Barak Korren created OVIRT-2307: ----------------------------------- Summary: JJB jobs cannot properly use SSL Key: OVIRT-2307 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2307 Project: oVirt - virtualization made easy Issue Type: Bug Components: JJB Reporter: Barak Korren Assignee: infra Priority: High Our JJB jobs cannot properly use SSL ATM because the way we install JJB (inside a Python virtualenv with on system packages) makes the requests library it uses for HTTP to not know how to find the trusted CAs bundle file. The way to solve this is to set the following variable in the JJB environment: {code} export REQUESTS_CA_BUNDLE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem {code} -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2306) rebuild staging HC hosts as bare metal slaves
by Evgheni Dereveanchin (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2306?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2306: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > rebuild staging HC hosts as bare metal slaves > --------------------------------------------- > > Key: OVIRT-2306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2306 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > We need more bare metal slaves to run lago workloads. We can rebuild the three systems that take part of the HyperConverged staging environment: > * ovirt-srv06 > * ovirt-srv07 > * ovirt-srv08 > Opening ticket to rebuild them and add to Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2306) rebuild staging HC hosts as bare metal slaves
by Evgheni Dereveanchin (oVirt JIRA) 11 Jul '18

11 Jul '18

Evgheni Dereveanchin created OVIRT-2306: ------------------------------------------- Summary: rebuild staging HC hosts as bare metal slaves Key: OVIRT-2306 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2306 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra We need more bare metal slaves to run lago workloads. We can rebuild the three systems that take part of the HyperConverged staging environment: * ovirt-srv06 * ovirt-srv07 * ovirt-srv08 Opening ticket to rebuild them and add to Jenkins. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[CQ]: 4217ba1 (ovirt-ansible-disaster-recovery) failed "ovirt-4.2" system tests
by oVirt Jenkins 11 Jul '18

11 Jul '18

Change 4217ba1 (ovirt-ansible-disaster-recovery) is probably the reason behind recent system test failures in the "ovirt-4.2" 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-disaster-recovery/commit/4217ba1b6e4… For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2620/

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Dafna Ron (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2193: ---------------------------------- [~dfediuck] [~eedri], [~gbenhaim(a)redhat.com] and I were discussing this yesterday. The majority of the current failed tests that are marked as "race" are caused due to locks and tasks cleanup in engine and we should not be failing the tests if they are modified to query tasks/locked objects before command is run and fail on query timeout. The Network team fixed their testes which were failing on similar issues and I am happy to say it reduced these sort of failures for network. The majority of these failures today are in storage related tests which [~tnisan(a)redhat.com] has been notified and has assigned [~derez(a)redhat.com] to look at. However, if I continue to see these tests failing sporadically (and I mean a test that is failing sporadically over a period of a month) I may have to skip those tests until they are fixed. We can improve on deciding what is an expectable % of failures and for what period of time we should quantify it before we skip the tests and decide on a cooperation with developers regarding the tests ownership (i.e maybe have a point of contact on each team for ost) > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

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

11 Jul '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: 323 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #323 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 1

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2193: ---------------------------------- We need to try to formalize some process around it, I'm not talking about one-time failures, its tests that fail every once in a while. There are not "environment" issues, this is isolated Lago run, so the chance of that happening is very low. We also filter out any issues that are infra related, so only if a real code race happens, we open a ticket and mark it as 'race'. If developers need more info/logs/insights then they should ask for it, otherwise, I think that we'll just start disabling tests that fail too often, this is taking a heavy toll on monitoring and manual work from the team, we need to improve the current handling of race failures. > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Doron Fediuck (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Doron Fediuck commented on OVIRT-2193: -------------------------------------- A race by definition may or may not materialize. If it's consistent that's an easy thing to fix. If it's not, We need some more insights than the end result. For example, is there an environmental issue, etc. > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2055) failure in suspend resume vm not related to reported change - need to investigate
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2055?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2055: ---------------------------------- Did you ask someone from virt team? was [~mskrivanek] notified on this? > failure in suspend resume vm not related to reported change - need to investigate > --------------------------------------------------------------------------------- > > Key: OVIRT-2055 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2055 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > Change 91507,1 (ovirt-engine-sdk-java) 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/91507/1 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7721/ > I think the issue is on qemu/libvirt changed queries: > https://pastebin.com/afyeUAcT > https://pastebin.com/va20Y5Hp > checking his with vdsm people. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2193) vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2193: ---------------------------------- [~dfediuck] we seem to be getting race failures like that often, which makes it very hard to enable reporting back to Gerrit to finding a resolution. We can't continue with the approach of "no reason for it to fail, its a race" and stop the debugging process there. There has to be a more in depth investigation from development side if we want to start reducing these races. > vdsm project CQ failure: 004_basic_sanity.preview_snapshot_with_memory > ---------------------------------------------------------------------- > > Key: OVIRT-2193 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2193 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > we have a failed vdsm test in basic master suite. > 004_basic_sanity.preview_snapshot_with_memory > seems like a regression. > ' 2018-06-12 07:31:08,080-04 DEBUG [org.ovirt.engine.core.aaa.filters.SsoRestApiNegotiationFilter] (default task-27) [] SsoRestApiNegotiationFilter Not performing Negotiate Auth > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Input validation failed while processing 'POST' request for path '/vms/ec6dcfb7-dda9-4c58-b048-87b08ffcbfbe > /previewsnapshot'. > 2018-06-12 07:31:08,087-04 ERROR [org.ovirt.engine.api.restapi.resource.validation.ValidationExceptionMapper] (default task-27) [] Exception: org.ovirt.api.metamodel.server.ValidationException: Parameter 'snapshot.id' is mandatory but was > not provided. > at org.ovirt.engine.api.resource.VmResourceHelper.validatePreviewSnapshot(VmResourceHelper.java:75) [restapi-definition.jar:] > at org.ovirt.engine.api.resource.VmResource.doPreviewSnapshot(VmResource.java:333) [restapi-definition.jar:] > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) [rt.jar:1.8.0_171] > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) [rt.jar:1.8.0_171] > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) [rt.jar:1.8.0_171] > at java.lang.reflect.Method.invoke(Method.java:498) [rt.jar:1.8.0_171]' > Change 90532,7 (vdsm) 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/90532/7 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8169/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2195) race in 004_basic_sanity.verify_vm_import on master CQ
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2195?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2195: ---------------------------------- Another open isssue that is open for almost a month, we have to see how we shorten the cycle here. Dafna, please escalate if you don't get a reply or resolution from the relevant maintainer after a few days. If Shmuel is checking it, he needs to assigned to this ticket and provide a result after a few days max. FYI [~dfediuck] > race in 004_basic_sanity.verify_vm_import on master CQ > ------------------------------------------------------ > > Key: OVIRT-2195 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2195 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > We have a race that causes test: 004_basic_sanity.verify_vm_import to fail > This build: https://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8183/ failed but there is nothing in the log to suggest that the import failed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2202) 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2202?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2202: ---------------------------------- This is open for almost a month, I don't think we still even have logs to look at them? [~dron] if you can't get a resolution or response on an error, please let me know on the same week, so we can escalate. Right now you can probably close it as can't reproduce. > 006_migrations.prepare_migration_attachments_ipv4 for ovirt-engine-dashboard > ---------------------------------------------------------------------------- > > Key: OVIRT-2202 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2202 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_race > > There was a failed test 006_migrations.prepare_migration_attachments_ipv4 > Error: The response content type 'text/html; charset=iso-8859-1' isn't the expected XML > Build: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8208/ > patch reported: https://gerrit.ovirt.org/#/c/92238/1 - add resolutions section to force jquery and bootstrap versions > The actual error is: Unable to process messages Broken pipe: java.io.IOException: Broken pipe > this would be the error in vdsm: > '2018-06-14 04:05:34,698-0400 ERROR (jsonrpc/5) [vds] connectivity check failed (API:1537) > Traceback (most recent call last): > File "/usr/lib/python2.7/site-packages/vdsm/API.py", line 1534, in setupNetworks > supervdsm.getProxy().setupNetworks(networks, bondings, options) > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 56, in __call__ > return callMethod() > File "/usr/lib/python2.7/site-packages/vdsm/common/supervdsm.py", line 54, in <lambda> > **kwargs) > File "<string>", line 2, in setupNetworks > File "/usr/lib64/python2.7/multiprocessing/managers.py", line 773, in _callmethod > raise convert_to_error(kind, result) > ConfigNetworkError: (10, 'connectivity check failed') > 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [api.network] FINISH setupNetworks return={'status': {'message': 'connectivity check failed', 'code': 10}} from=::ffff:192.168.201.4,50952 (api:53) > 2018-06-14 04:05:34,699-0400 INFO (jsonrpc/5) [jsonrpc.JsonRpcServer] RPC call Host.setupNetworks failed (error 10) in 127.20 seconds (__init__:311)' > The patch may be related so I will as Greg to take a look -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2203) failure in update host caused patch to fail
by Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2203?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2203: ---------------------------------- [~sbonazzo(a)redhat.com] who can look at the upgrade logs and see if there is a bug there? > failure in update host caused patch to fail > ------------------------------------------- > > Key: OVIRT-2203 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2203 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra, ost_race > > The patch failed due to failure to update the host: > '2018-06-14 08:25:38,754-04 ERROR [org.ovirt.engine.core.bll.host.HostUpgradeManager] (EE-ManagedThreadFactory-commandCoordinator-Thread-1) [cb22fd71-b94d-4567-a8e4-78238868d2de] Failed to run check-update of host 'lago-basic-suite-master- > host-0'' > I can see that the upgrade suite also failed for not seeing repos > The next metrics build succeeded successfully so there is no need to do anything > I cannot be sure but I think its probably a network glitch or jenkins issue which happened during the test run. > here is the info from the mail: > Change 92195,2 (ovirt-engine-metrics) 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/92195/2 > For failed test results see: > http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/8213/ -- 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 Eyal Edri (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2264: ---------------------------------- [~derez@redhat.com][~tnisan@redhat.com] any update? > 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 > Labels: ost_failures, ost_race > > 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-2275) Finish to update "How to run OST" docs
by Greg Sheremeta (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2275?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-2275: --------------------------------------- Sorry, I gave up and deleted the environment. > Finish to update "How to run OST" docs > -------------------------------------- > > Key: OVIRT-2275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2275 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > We need to finish updating https://gerrit.ovirt.org/#/c/90523/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2305) Clean up dead slaves from the staging Jenkins
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

Barak Korren created OVIRT-2305: ----------------------------------- Summary: Clean up dead slaves from the staging Jenkins Key: OVIRT-2305 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2305 Project: oVirt - virtualization made easy Issue Type: Outage Components: Staging infra Reporter: Barak Korren Assignee: infra -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2304?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2304: -------------------------------- Issue Type: Improvement (was: New Feature) > Make usrc.py list all the added US patches in the commit message not the last one > --------------------------------------------------------------------------------- > > Key: OVIRT-2304 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > > When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. > This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. > It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2304?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2304: -------------------------------- Issue Type: New Feature (was: Outage) > Make usrc.py list all the added US patches in the commit message not the last one > --------------------------------------------------------------------------------- > > Key: OVIRT-2304 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: usrc.py > Reporter: Barak Korren > Assignee: infra > > When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. > This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. > It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2304) Make usrc.py list all the added US patches in the commit message not the last one
by Barak Korren (oVirt JIRA) 11 Jul '18

11 Jul '18

Barak Korren created OVIRT-2304: ----------------------------------- Summary: Make usrc.py list all the added US patches in the commit message not the last one Key: OVIRT-2304 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2304 Project: oVirt - virtualization made easy Issue Type: Outage Components: usrc.py Reporter: Barak Korren Assignee: infra When running the '{{usrc.py update --commit}}' command, it creates a commit message that includes various details about the patch that was linked to in '{{upstream-sources.yaml}}'. This commit message does not really show the full picture for the change that is really being done to the DS repo, as when updating '{{upstream-sources.yaml}}', the effictive change to the repo is the sub of all commits between the new commit that is added to '{{upstream-sources.yaml}}' and the one that was there before. It is desirable to list all the US commits between the previous one to the updated one in the commit message so that it is easier to understand the extent of the actual change that was made. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

oVirt infra daily report - unstable production jobs - 517
by jenkins＠jenkins.phx.ovirt.org 11 Jul '18

11 Jul '18

Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/517//artifact/exported-a… Cheers, Jenkins

1 0

[oVirt Jenkins] ovirt-system-tests_he-basic-suite-master - Build # 591 - Failure!
by jenkins＠jenkins.phx.ovirt.org 11 Jul '18

11 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-suite-master/591/ Build Number: 591 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #591 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 1

[oVirt Jenkins] ovirt-system-tests_he-basic-iscsi-suite-4.2 - Build # 112 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_he-basic-iscsi-suite-4.2/11… Build Number: 112 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #112 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- All tests passed

1 1

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

10 Jul '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: 320 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #320 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- No tests ran.

1 2

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs
by Yuval Turgeman (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-2287: --------------------------------------- Gal took care of this already - https://gerrit.ovirt.org/#/c/92902/ :) On Tue, Jul 10, 2018, 18:59 Dafna Ron <dron(a)redhat.com> wrote: > host memory is 4720 for both hosts. since one is running the engine should > we increase it? > > {%- for i in range(hostCount) %} > lago-{{ env.suite_name }}-host-{{ i }}: > vm-type: ovirt-host > distro: el7 > service_provider: systemd > memory: 4720 > > > > On Sun, Jul 8, 2018 at 7:38 AM, Barak Korren <bkorren(a)redhat.com> wrote: > >> >> >> On 6 July 2018 at 11:57, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: >> >>> >>> >>> https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… >>> >>> Cannot run VM. There is no host that satisfies current scheduling >>> constraints. See below for details:, The host >>> lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory >>> because its available memory is too low (656 MB) to run the VM. >>> >>> >> >> this sounds like something that needs to be fixed in the suit's >> LagoInitFile. >> >> >> >>> -- >>> >>> SANDRO BONAZZOLA >>> >>> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >>> >>> Red Hat EMEA <https://www.redhat.com/> >>> >>> sbonazzo(a)redhat.com >>> <https://red.ht/sig> >>> >>> _______________________________________________ >>> Devel mailing list -- devel(a)ovirt.org >>> To unsubscribe send an email to devel-leave(a)ovirt.org >>> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >>> oVirt Code of Conduct: >>> https://www.ovirt.org/community/about/community-guidelines/ >>> List Archives: >>> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/TDKLML6YDBATF… >>> >>> >> >> >> -- >> Barak Korren >> RHV DevOps team , RHCE, RHCi >> Red Hat EMEA >> redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted >> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/S6F3JGB3C5OSK… >> >> > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/devel@ovirt.org/message/CUT2OW3NUPU26… > > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2303) decommission and remove alterway02
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2303?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2303: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > decommission and remove alterway02 > ---------------------------------- > > Key: OVIRT-2303 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2303 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The last workload on the old Alterway oVirt deployment was removed so it's now time to fully decommission the system, power it down and remove all of its leftovers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2303) decommission and remove alterway02
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

Evgheni Dereveanchin created OVIRT-2303: ------------------------------------------- Summary: decommission and remove alterway02 Key: OVIRT-2303 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2303 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra The last workload on the old Alterway oVirt deployment was removed so it's now time to fully decommission the system, power it down and remove all of its leftovers. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2283) add router monitoring to nagios
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2283?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2283: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > add router monitoring to nagios > ------------------------------- > > Key: OVIRT-2283 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2283 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > We need to monitor the PHX router and define the topology to see datacenter-wide outages -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2287: ---------------------------------- host memory is 4720 for both hosts. since one is running the engine should we increase it? {%- for i in range(hostCount) %} lago-{{ env.suite_name }}-host-{{ i }}: vm-type: ovirt-host distro: el7 service_provider: systemd memory: 4720 On Sun, Jul 8, 2018 at 7:38 AM, Barak Korren <bkorren(a)redhat.com> wrote: > > > On 6 July 2018 at 11:57, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote: > >> >> https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng- >> suite-master/165/testReport/(root)/004_basic_sanity/vm_run/ >> >> Cannot run VM. There is no host that satisfies current scheduling >> constraints. See below for details:, The host lago-he-node-ng-suite-master-host-0 >> did not satisfy internal filter Memory because its available memory is too >> low (656 MB) to run the VM. >> >> > > this sounds like something that needs to be fixed in the suit's > LagoInitFile. > > > >> -- >> >> SANDRO BONAZZOLA >> >> MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV >> >> Red Hat EMEA <https://www.redhat.com/> >> >> sbonazzo(a)redhat.com >> <https://red.ht/sig> >> >> _______________________________________________ >> Devel mailing list -- devel(a)ovirt.org >> To unsubscribe send an email to devel-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/site/privacy-policy/ >> oVirt Code of Conduct: https://www.ovirt.org/communit >> y/about/community-guidelines/ >> List Archives: https://lists.ovirt.org/archiv >> es/list/devel(a)ovirt.org/message/TDKLML6YDBATFHS232GFJF7QVRTWUH74/ >> >> > > > -- > Barak Korren > RHV DevOps team , RHCE, RHCi > Red Hat EMEA > redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted > > _______________________________________________ > Devel mailing list -- devel(a)ovirt.org > To unsubscribe send an email to devel-leave(a)ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > guidelines/ > List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/ > message/S6F3JGB3C5OSKNWMM3THXMIR2XYYUOGO/ > > > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[oVirt Jenkins] ovirt-system-tests_network-suite-master - Build # 376 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jul '18

10 Jul '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_network-suite-master/376/ Build Number: 376 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #376 [Sandro Bonazzola] master: consume qemu-kvm-ev test builds ----------------- Failed Tests: ----------------- No tests ran.

1 3

[JIRA] (OVIRT-2275) Finish to update "How to run OST" docs
by Gal Ben Haim (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2275?page=com.atlassian.jira.… ] Gal Ben Haim commented on OVIRT-2275: ------------------------------------- [~gshereme(a)redhat.com] I don't want that the docs will block you. What is the error that you see? > Finish to update "How to run OST" docs > -------------------------------------- > > Key: OVIRT-2275 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2275 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > We need to finish updating https://gerrit.ovirt.org/#/c/90523/ -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2302) improve cleanup of stuck livemedia-creator processes
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2302?page=com.atlassian.jira.… ] Evgheni Dereveanchin edited comment on OVIRT-2302 at 7/10/18 2:41 PM: ---------------------------------------------------------------------- Job log from OVIRT-2289: 13:39:34 [check-patch.fc28.x86_64] Cancelling nested steps due to timeout 13:39:34 [check-patch.fc28.x86_64] Sending interrupt signal to process 13:39:34 [check-patch.fc28.x86_64] sh: line 1: 50927 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/script.sh' > '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/jenkins-log.txt' 2>&1 13:39:44 [check-patch.fc28.x86_64] After 10s process did not stop ... leftover process #1: /usr/bin/python3 /usr/sbin/livemedia-creator --make-pxe-live --iso boot.iso --ks data/ovirt-node-ng-image.ks --resultdir build --tmp /var/tmp leftover process #2 (child of #1): qemu-system-x86_64 -nodefconfig -m 1024 --machine accel=kvm -kernel /var/tmp/lorax.imgutils._0vdnawj/isolinux/vmlinuz -initrd /var/tmp/lmc-initrd-t7xhq9lb.img -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/build/lmc-disk-57z7t8fn.img,cache=unsafe,discard=unmap,format=raw -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/boot.iso,media=cdrom,readonly=on -append ks=file:/ovirt-node-ng-image.ks inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 inst.text inst.cmdline -nographic -display vnc=127.0.0.1:0 -device virtio-serial-pci,id=virtio-serial0 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.fedoraproject.anaconda.log.0 -chardev socket,id=charchannel0,host=127.0.0.1,port=37582 -object rng-random,id=virtio-rng0,filename=/dev/random -device virtio-rng-pci,rng=virtio-rng0,id=rng0,bus=pci.0,addr=0x9 full process tree: mock - sh - sudo - make - livemedia-creat - qemu-system-x86 was (Author: ederevea): Job log from OVIRT-2289: 13:39:34 [check-patch.fc28.x86_64] Cancelling nested steps due to timeout 13:39:34 [check-patch.fc28.x86_64] Sending interrupt signal to process 13:39:34 [check-patch.fc28.x86_64] sh: line 1: 50927 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/script.sh' > '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/jenkins-log.txt' 2>&1 13:39:44 [check-patch.fc28.x86_64] After 10s process did not stop ... leftover process #1: /usr/bin/python3 /usr/sbin/livemedia-creator --make-pxe-live --iso boot.iso --ks data/ovirt-node-ng-image.ks --resultdir build --tmp /var/tmp leftover process #2 (child of #1): qemu-system-x86_64 -nodefconfig -m 1024 --machine accel=kvm -kernel /var/tmp/lorax.imgutils._0vdnawj/isolinux/vmlinuz -initrd /var/tmp/lmc-initrd-t7xhq9lb.img -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/build/lmc-disk-57z7t8fn.img,cache=unsafe,discard=unmap,format=raw -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/boot.iso,media=cdrom,readonly=on -append ks=file:/ovirt-node-ng-image.ks inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 inst.text inst.cmdline -nographic -display vnc=127.0.0.1:0 -device virtio-serial-pci,id=virtio-serial0 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.fedoraproject.anaconda.log.0 -chardev socket,id=charchannel0,host=127.0.0.1,port=37582 -object rng-random,id=virtio-rng0,filename=/dev/random -device virtio-rng-pci,rng=virtio-rng0,id=rng0,bus=pci.0,addr=0x9 full proccesstree: mock---sh-+-sh-+-sudo---make---livemedia-creat-+-qemu-system-x86---3*[{qemu-system-x86}] > improve cleanup of stuck livemedia-creator processes > ---------------------------------------------------- > > Key: OVIRT-2302 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2302 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > The following job timed out yet the cleanup wasn't performed properly for it: > https://jenkins.ovirt.org/job/ovirt-node-ng_standard-check-patch/5/consoleF… > After the cleanup, livemedia-creator and a qemu process were still running and consuming memory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2302) improve cleanup of stuck livemedia-creator processes
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2302?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-2302: --------------------------------------------- Job log from OVIRT-2289: 13:39:34 [check-patch.fc28.x86_64] Cancelling nested steps due to timeout 13:39:34 [check-patch.fc28.x86_64] Sending interrupt signal to process 13:39:34 [check-patch.fc28.x86_64] sh: line 1: 50927 Terminated JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/script.sh' > '/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng(a)tmp/durable-2af3df32/jenkins-log.txt' 2>&1 13:39:44 [check-patch.fc28.x86_64] After 10s process did not stop ... leftover process #1: /usr/bin/python3 /usr/sbin/livemedia-creator --make-pxe-live --iso boot.iso --ks data/ovirt-node-ng-image.ks --resultdir build --tmp /var/tmp leftover process #2 (child of #1): qemu-system-x86_64 -nodefconfig -m 1024 --machine accel=kvm -kernel /var/tmp/lorax.imgutils._0vdnawj/isolinux/vmlinuz -initrd /var/tmp/lmc-initrd-t7xhq9lb.img -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/build/lmc-disk-57z7t8fn.img,cache=unsafe,discard=unmap,format=raw -drive file=/home/jenkins/workspace/ovirt-node-ng_standard-check-patch/ovirt-node-ng/boot.iso,media=cdrom,readonly=on -append ks=file:/ovirt-node-ng-image.ks inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-28 inst.text inst.cmdline -nographic -display vnc=127.0.0.1:0 -device virtio-serial-pci,id=virtio-serial0 -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.fedoraproject.anaconda.log.0 -chardev socket,id=charchannel0,host=127.0.0.1,port=37582 -object rng-random,id=virtio-rng0,filename=/dev/random -device virtio-rng-pci,rng=virtio-rng0,id=rng0,bus=pci.0,addr=0x9 full proccesstree: mock---sh-+-sh-+-sudo---make---livemedia-creat-+-qemu-system-x86---3*[{qemu-system-x86}] > improve cleanup of stuck livemedia-creator processes > ---------------------------------------------------- > > Key: OVIRT-2302 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2302 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Evgheni Dereveanchin > Assignee: infra > > The following job timed out yet the cleanup wasn't performed properly for it: > https://jenkins.ovirt.org/job/ovirt-node-ng_standard-check-patch/5/consoleF… > After the cleanup, livemedia-creator and a qemu process were still running and consuming memory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2302) improve cleanup of stuck livemedia-creator processes
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

Evgheni Dereveanchin created OVIRT-2302: ------------------------------------------- Summary: improve cleanup of stuck livemedia-creator processes Key: OVIRT-2302 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2302 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Evgheni Dereveanchin Assignee: infra The following job timed out yet the cleanup wasn't performed properly for it: https://jenkins.ovirt.org/job/ovirt-node-ng_standard-check-patch/5/consoleF… After the cleanup, livemedia-creator and a qemu process were still running and consuming memory. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Evgheni Dereveanchin (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2301: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > cq job stuck for 6 days > ----------------------- > > Key: OVIRT-2301 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: Evgheni Dereveanchin > Labels: ost_failures, ost_infra > > [~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ > The job got stuck while waiting for build-artifacts: > http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-… > before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)redhat.com] would like to take a look. > the job is still reported as active -- 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 Tal Nisan (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Tal Nisan commented on OVIRT-2264: ---------------------------------- [~derez(a)redhat.com] you are the current QE contact, can you please have a look? > 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 > Labels: ost_failures, ost_race > > 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-2301) cq job stuck for 6 days
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2301: ------------------------------------- The full job log tells you the right story: {code} Resuming build at Wed Jul 04 18:30:12 UTC 2018 after Jenkins restart Waiting to resume part of ovirt-4.2_change-queue-tester #2570: ??? [Pipeline] End of Pipeline java.lang.IllegalStateException: JENKINS-37121: something already locked /home/jenkins/workspace/ovirt-4.2_change-queue-tester at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:75) at org.jenkinsci.plugins.workflow.support.pickles.WorkspaceListLeasePickle$1.tryResolve(WorkspaceListLeasePickle.java:51) at org.jenkinsci.plugins.workflow.support.pickles.TryRepeatedly$1.run(TryRepeatedly.java:92) at jenkins.security.ImpersonatingScheduledExecutorService$1.run(ImpersonatingScheduledExecutorService.java:58) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) Caused: java.io.IOException: Failed to load build state at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:854) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$3.onSuccess(CpsFlowExecution.java:852) at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution$4$1.run(CpsFlowExecution.java:906) at org.jenkinsci.plugins.workflow.cps.CpsVmExecutorService$1.run(CpsVmExecutorService.java:35) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) at jenkins.security.ImpersonatingExecutorService$1.run(ImpersonatingExecutorService.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE {code} > cq job stuck for 6 days > ----------------------- > > Key: OVIRT-2301 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > [~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ > The job got stuck while waiting for build-artifacts: > http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-… > before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)redhat.com] would like to take a look. > the job is still reported as active -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Barak Korren (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2301?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2301: ------------------------------------- Nothing can be stuck for 6 days (we have timeouts defined) - if it is it means jenkins was shut down while it was running (which can cause pipeline jobs for freeze and not resume), and it should be aborted. Although by the looks of it, this might have run while using a buggy modified version of the pipeline code, [~dbelenky(a)redhat.com] can you confirm? > cq job stuck for 6 days > ----------------------- > > Key: OVIRT-2301 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Dafna Ron > Assignee: infra > Labels: ost_failures, ost_infra > > [~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ > The job got stuck while waiting for build-artifacts: > http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-… > before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)redhat.com] would like to take a look. > the job is still reported as active -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2301) cq job stuck for 6 days
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

Dafna Ron created OVIRT-2301: -------------------------------- Summary: cq job stuck for 6 days Key: OVIRT-2301 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2301 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Dafna Ron Assignee: infra [~ederevea] noticed that this job has been stuck for 6 days: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/2570/ The job got stuck while waiting for build-artifacts: http://jenkins.ovirt.org/blue/organizations/jenkins/ovirt-4.2_change-queue-… before he restarts jenkins I though [~bkorren(a)redhat.com] or [~dbelenky(a)redhat.com] would like to take a look. the job is still reported as active -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2287) ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2287?page=com.atlassian.jira.… ] Dafna Ron commented on OVIRT-2287: ---------------------------------- I will look at the Lagoinit file and submit a patch. > ovirt-system-tests_he-node-ng-suite-master is failing on not enough memory to run VMs > ------------------------------------------------------------------------------------- > > Key: OVIRT-2287 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2287 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: sbonazzo > Assignee: infra > Priority: Highest > Labels: ost_failures, ost_lago > Attachments: srv.log > > > https://jenkins.ovirt.org/job/ovirt-system-tests_he-node-ng-suite-master/16… > Cannot run VM. There is no host that satisfies current scheduling > constraints. See below for details:, The host > lago-he-node-ng-suite-master-host-0 did not satisfy internal filter Memory > because its available memory is too low (656 MB) to run the VM. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2300?page=com.atlassian.jira.… ] Ehud Yonasi reassigned OVIRT-2300: ---------------------------------- Assignee: Ehud Yonasi (was: infra) > tested was corrupted > -------------------- > > Key: OVIRT-2300 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: Ehud Yonasi > Labels: cq-issue-traking, ost_failures, tested > > tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. > the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2300?page=com.atlassian.jira.… ] Ehud Yonasi updated OVIRT-2300: ------------------------------- Resolution: Fixed Status: Done (was: To Do) > tested was corrupted > -------------------- > > Key: OVIRT-2300 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Ehud Yonasi > Assignee: infra > Labels: cq-issue-traking, ost_failures, tested > > tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. > the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2300) tested was corrupted
by Ehud Yonasi (oVirt JIRA) 10 Jul '18

10 Jul '18

Ehud Yonasi created OVIRT-2300: ---------------------------------- Summary: tested was corrupted Key: OVIRT-2300 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2300 Project: oVirt - virtualization made easy Issue Type: Outage Reporter: Ehud Yonasi Assignee: infra tested partition got corrupted due to a mistake i've made in the cleanup retention policy ticket. the issue has been fixed and tested was restored from snapshots. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs
by Dafna Ron (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2299?page=com.atlassian.jira.… ] Dafna Ron reassigned OVIRT-2299: -------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > permissions to execute manual jenkins jobs > ------------------------------------------ > > Key: OVIRT-2299 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2299 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Miguel Duarte de Mora Barroso > Assignee: Evgheni Dereveanchin > > Hello, > I would like to run ovirt system tests on jenkins targeting other > builds - e.g. ovirt-provider-ovn / engine rpms generated in other > builds. > From what I've understood, I need to run the test suite, configuring > it with the target build url in the build parameters (accessed through > 'build with parameters' tab. > I can't find that, which leads me to believe I don't have permissions > to execute the builds myself. Could I be grantted enough permissions > to execute this use case? > If I'm wrong and this stems from other causes, let me know. > My jenkins user ID is mbarroso. > Thanks in advance, > Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2299) permissions to execute manual jenkins jobs
by Miguel Duarte de Mora Barroso (oVirt JIRA) 10 Jul '18

10 Jul '18

Miguel Duarte de Mora Barroso created OVIRT-2299: ---------------------------------------------------- Summary: permissions to execute manual jenkins jobs Key: OVIRT-2299 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2299 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Miguel Duarte de Mora Barroso Assignee: infra Hello, I would like to run ovirt system tests on jenkins targeting other builds - e.g. ovirt-provider-ovn / engine rpms generated in other builds. From what I've understood, I need to run the test suite, configuring it with the target build url in the build parameters (accessed through 'build with parameters' tab. I can't find that, which leads me to believe I don't have permissions to execute the builds myself. Could I be grantted enough permissions to execute this use case? If I'm wrong and this stems from other causes, let me know. My jenkins user ID is mbarroso. Thanks in advance, Miguel -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0

[JIRA] (OVIRT-2201) [regression] STDCI v2 doesn't distinguish jobs for different branches
by Yuval Turgeman (oVirt JIRA) 10 Jul '18

10 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2201?page=com.atlassian.jira.… ] Yuval Turgeman commented on OVIRT-2201: --------------------------------------- For ovirt-node-ng, we generate a latest-installation-iso.html in build-artifacts, and the download page[1] points to the last successful build per ovirt version. It looks like we can't do it in V2 today. [1] https://www.ovirt.org/node/ > [regression] STDCI v2 doesn't distinguish jobs for different branches > --------------------------------------------------------------------- > > Key: OVIRT-2201 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2201 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Standard CI (Pipelines) > Reporter: sbonazzo > Assignee: infra > > In V1 we had jobs with different name based on branches they were building. > In V2 we have single job building all branches. > As an example for imgbased: > https://jenkins.ovirt.org/job/imgbased_standard-on-merge/lastSuccessfulBuil… > will contain randomly 4.2 or master builds. > This won't allow to filter jenkins to see which branches are failing to > build, forcing developers to check manually. > This also won't allow to check if latest build landed in tested repo > because thee build may be targeted to a different branch than the one under > check. > To me this is a regression that will make me rethink about the switching to > v2 and considering reverting to v1. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100088)

1 0