Ask Your Question
0

VMware stuck in building state with Borken Pipe on initial image copy

asked 2015-03-17 10:42:12 -0500

jjulien gravatar image

I'm getting the following error in my nova log trying to launch my first VMware instance. I ran a network trace and found that the vCenter server was issuing a conneciton reset. I could not find anything in vCenter logs. The VM itself gets stuck in a building state. It does exist in vCenter, so that validates the that the vmware driver is able to talk through the vCenter API. Anyone know what might be causing this?

HTTP/1.1 200 OK
content-length: 18874368
date: Tue, 17 Mar 2015 13:26:05 GMT
x-image-meta-status: active
x-image-meta-owner: 416b49c371cb4b5ca05deea5c340104b
x-image-meta-name: vmware-cirros
x-image-meta-container_format: bare
x-image-meta-created_at: 2015-03-09T18:27:35.799380
etag: 67d4fd3785344b673334dbc6c1010519
x-image-meta-min_ram: 0
x-image-meta-hypervisor_type: vmware
x-image-meta-vmware_disktype: sparse
x-image-meta-id: e8f88033-f0c6-4120-a675-6153dc4a6fa8
x-image-meta-vmware_adaptertype: ide
x-openstack-request-id: req-a5c87a1e-48ab-4c1a-b72a-c355e11bdd96
x-image-meta-updated_at: 2015-03-09T18:30:06.674129
x-image-meta-deleted: False
x-image-meta-checksum: 67d4fd3785344b673334dbc6c1010519
x-image-meta-protected: False
x-image-meta-min_disk: 0
x-image-meta-size: 18874368
x-image-meta-is_public: True
content-type: application/octet-stream
x-image-meta-disk_format: vmdk
 log_http_response /usr/lib/python2.7/site-packages/glanceclient/common/http.py:135
2015-03-17 08:26:05.171 32053 ERROR nova.virt.vmwareapi.io_util [-] [Errno 32] Broken pipe
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util Traceback (most recent call last):
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib/python2.7/site-packages/nova/virt/vmwareapi/io_util.py", line 179, in _inner
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     self.output.write(data)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib/python2.7/site-packages/nova/virt/vmwareapi/read_write_util.py", line 137, in write
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     self.file_handle.send(data)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib64/python2.7/httplib.py", line 805, in send
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     self.sock.sendall(data)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib/python2.7/site-packages/eventlet/green/ssl.py", line 137, in sendall
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     v = self.send(data[count:])
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib/python2.7/site-packages/eventlet/green/ssl.py", line 113, in send
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     super(GreenSSLSocket, self).send, data, flags)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib/python2.7/site-packages/eventlet/green/ssl.py", line 80, in _call_trampolining
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     return func(*a, **kw)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util   File "/usr/lib64/python2.7/ssl.py", line 198, in send
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util     v = self._sslobj.write(data)
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util error: [Errno 32] Broken pipe
2015-03-17 08:26:05.171 32053 TRACE nova.virt.vmwareapi.io_util
edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted
0

answered 2015-03-19 08:02:56 -0500

jjulien gravatar image

I have tracked down this error. The "Broken Pipe" is due to vCenter hard cutting off connections that attempt to do large PUT operations where a 404 error would be returned. Rather then accepting the payload and returning the 404 it just resets the connection.

So, the reason for the 404 error is due to a known bug in the VMware driver when trying to upload images to a Datacenter that does not reside in the root folder in vCenter.

https://bugs.launchpad.net/nova/+bug/1369019 (https://bugs.launchpad.net/nova/+bug/...)

Moving the datacenter to the root folder resolved the issue.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-03-17 10:42:12 -0500

Seen: 2,805 times

Last updated: Mar 19 '15