Vmware vcenter connection session timeout serveral hours later after cinder-volume is started

Bug #1330353 reported by Kai Tong
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Cinder
New
Undecided
Unassigned

Bug Description

I have configured a cinder-volume to point to a vmware vcenter, at first it works well when I try to create volume. But after many hours the connection timeout and when I create volume and below error thrown out:

2014-06-15 22:51:06.005 10392 INFO cinder.volume.flows.manager.create_volume [req-aee9e3f8-ba6f-47ef-a225-3ec56f4670cb d108fd6c885341059a57fc58673163d0 473dafb0592c449387c1dfd772f51a8d - - -] CN-E562449 Volume 9e881fd5-f0b2-4dee-a0e8-cd76e912c6cf: being created using CreateVolumeFromSpecTask._create_raw_volume with specification: {'status': u'creating', 'volume_size': 1, 'volume_name': u'volume-9e881fd5-f0b2-4dee-a0e8-cd76e912c6cf'}
2014-06-15 22:51:06.113 10392 DEBUG cinder.volume.drivers.vmware.api [-] CN-66671FE Checking if the current session: 526c24e8-cf1a-133f-02ee-1669c8e60442 is active. _is_current_session_active /usr/lib/python2.6/site-packages/cinder/volume/drivers/vmware/api.py:260
2014-06-15 22:51:06.165 10392 ERROR suds.client [-] <?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:ns0="urn:vim25" xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
   <ns1:Body>
      <ns0:SessionIsActive>
         <ns0:_this type="SessionManager">SessionManager</ns0:_this>
         <ns0:sessionID>526c24e8-cf1a-133f-02ee-1669c8e60442</ns0:sessionID>
         <ns0:userName>root</ns0:userName>
      </ns0:SessionIsActive>
   </ns1:Body>
</SOAP-ENV:Envelope>
2014-06-15 22:51:06.169 10392 ERROR cinder.openstack.common.loopingcall [-] CN-F18D768 in dynamic looping call
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall Traceback (most recent call last):
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall File "/usr/lib/python2.6/site-packages/cinder/openstack/common/loopingcall.py", line 123, in _inner
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall idle = self.f(*self.args, **self.kw)
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall File "/usr/lib/python2.6/site-packages/cinder/volume/drivers/vmware/api.py", line 82, in _func
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall raise excep
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall VimFaultException: Server raised fault: 'The session is not authenticated.'
2014-06-15 22:51:06.169 10392 TRACE cinder.openstack.common.loopingcall
2014-06-15 22:51:06.172 10392 DEBUG taskflow.storage [req-aee9e3f8-ba6f-47ef-a225-3ec56f4670cb d108fd6c885341059a57fc58673163d0 473dafb0592c449387c1dfd772f51a8d - - -] No backend provided, not calling functor 'taskflow.storage.SingleThreadedStorage._save_task_detail' _with_connection /usr/lib/python2.6/site-packages/taskflow/storage.py:88

Revision history for this message
Kai Tong (tongkai) wrote :
Revision history for this message
Kai Tong (tongkai) wrote :
Revision history for this message
David Geng (genggjh) wrote :

This is a duplicate defect, see 1302514

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.