[
https://ovirt-jira.atlassian.net/browse/OVIRT-2202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37873#comment-37873
]
Alona Kaplan commented on OVIRT-2202:
-------------------------------------
Hi, I've already talked about it with Dafna. The last race she found is caused
because of an event sent from the vdsm.
Due to a recent fix (https://bugzilla.redhat.com/1590109), now the event
mechanism actually works in the engine. And if the engine gets event from the
vdsm a getCaps is invoked on the host.
Since it's unpredictable when an event will arrive (it can happen when setting
dhcp on a host nic, when the dhcp lease is renewed, ...).
We have an open jira task planned for RHV sprint 4 to handle the issue in the
OST - https://projects.engineering.redhat.com/browse/RHV-2165
> 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)
_______________________________________________
Infra mailing list -- infra@ovirt.org
To unsubscribe send an email to infra-le...@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/infra@ovirt.org/message/TQ272BMKT2LX5N3HHOZWU6EK65QWF6VE/
