August 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2054: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) open for more than 2 weeks, will reopen if it happens again > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > 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/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2054) false change reported since package is not deployed on ost
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2054?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2054: ---------------------------------- I want to start a new policy of closing tickets if we don't get answers for 2 weeks or the issue isn't happening for 2 weeks. Otherwise we'll be swamped with tickets. If a race happens again, you can search for it in JIRA with ost_race to check if it happened in the past before opening a new ticket. > false change reported since package is not deployed on ost > ---------------------------------------------------------- > > Key: OVIRT-2054 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2054 > 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/ > The package is not deployed on OST so it could not have been the reason for failure. > + I am investigating the cause of failure but since we do not deploy the package on ost there is actually no chance that the failure was due to the change - hence its false report. > Is there a way to check if a project is deployed on ost? do we even need to run ost on it or can we skip it as long as the package is not actually tested? is there a way for me to check that somewhere? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

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

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2193: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) No replies from developers, closing. If this will reappear, another 2 week period will be set to get a possible debug or RCA from developers. > 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#100090)

1 0

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

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2193?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2193: ---------------------------------- [~dron] we can't keep chasing this, For now let's set a deadline of 2 weeks for get replies on races from developers. ( eventually we'll shorten it for one week ). if there isn't a maintainer that answers or provides info within a week, please close the ticket. > 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#100090)

1 0

[JIRA] (OVIRT-2444) jenkin's generic webhook times out
by Evgheni Dereveanchin (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2444?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-2444: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > jenkin's generic webhook times out > ---------------------------------- > > Key: OVIRT-2444 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2444 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Roy Golan > Assignee: Evgheni Dereveanchin > > After merging a pool request [1] I didn't see the check-merged working. I > went into the webhook section > and so that jenkins wasn't responding in time. > Also a simple 'curl http://jenkins.ovirt.org/generic-webhook-trigger/invoke' > doesn't return > [1] https://github.com/oVirt/ovirt-openshift-extensions/pull/60 > Please help > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2444) jenkin's generic webhook times out
by Evgheni Dereveanchin (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2444?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-2444: ---------------------------------------- Issue Type: Outage (was: By-EMAIL) > jenkin's generic webhook times out > ---------------------------------- > > Key: OVIRT-2444 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2444 > Project: oVirt - virtualization made easy > Issue Type: Outage > Reporter: Roy Golan > Assignee: infra > > After merging a pool request [1] I didn't see the check-merged working. I > went into the webhook section > and so that jenkins wasn't responding in time. > Also a simple 'curl http://jenkins.ovirt.org/generic-webhook-trigger/invoke' > doesn't return > [1] https://github.com/oVirt/ovirt-openshift-extensions/pull/60 > Please help > \R -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

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

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2195?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2195: ---------------------------------- [~smelamud(a)redhat.com] any update ? > 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#100090)

1 0

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

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2202?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2202: ---------------------------------- [~danken(a)redhat.com] [~alkaplan] any update? > 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#100090)

1 0

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

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2203?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2203: ----------------------------- Resolution: Cannot Reproduce Status: Done (was: To Do) closing until we see it again, logs are not available now. > 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#100090)

1 0

[JIRA] (OVIRT-2264) Cannot deactivate Storage while there are running tasks on this Storage
by Eyal Edri (oVirt JIRA) 21 Aug '18

21 Aug '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2264?page=com.atlassian.jira.… ] Eyal Edri commented on OVIRT-2264: ---------------------------------- [~gbenhaim(a)redhat.com] I remember Steven did a fix for that or something similar no? He's not in JIRA so I can't cc him. [~grosenth(a)redhat.com] can you reach out to Steven Rosenberg and ask if we can unskip this test now? > 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#100090)

1 0