invoke_api does not throw any exception when interface goes down and looses connectivity with vCenter

Bug #1564839 reported by Aman Kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
oslo.vmware
Fix Released
Undecided
Aman Kumar

Bug Description

We are running a script which uses oslo vmware library to get vCenter VM events using property collector method WaitForUpdatesEx. If we unplug the interface, the property Collector method does not return. Ideally it should throw connection lost exceptions. But the method blocked forever. Debugging further we found that there is no way user can specify the timeout and suds(request transport) component uses by oslo vmware assumes None and waits for ever. So there should be facility in oslo vmware to configure this timeout and it should passed to suds/request component.

we found from the logs that it blocks after following log:

Waiting for function oslo_vmware.api._invoke_api to return.^[[00m ^[[00;33mfrom (pid=3974) func /usr/local/lib/python2.7/dist-packages/oslo_vmware/api.py:128^[[00m

Revision history for this message
Aman Kumar (amank) wrote :

Review link can be found here:
https://review.openstack.org/#/c/330889/

Changed in oslo.vmware:
assignee: nobody → Aman Kumar (amank)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/oslo.vmware 2.15.0

This issue was fixed in the openstack/oslo.vmware 2.15.0 release.

Aman Kumar (amank)
Changed in oslo.vmware:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.