yahoo-eng-team team mailing list archive

Thread
Date
[Bug 1387074] Re: VMware: Failed to launch instance if vCenter is configured to listen to any port other than 443

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: OpenStack Infra <1387074@xxxxxxxxxxxxxxxxxx>
Date: Tue, 12 Apr 2016 21:00:10 -0000
Reply-to: Bug 1387074 <1387074@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx
Reviewed:  https://review.openstack.org/267450
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=55b442ce192e93a26d12064645aa95fd3661babb
Submitter: Jenkins
Branch:    master

commit 55b442ce192e93a26d12064645aa95fd3661babb
Author: Vipin Balachandran <vbala@xxxxxxxxxx>
Date:   Thu Jan 14 00:05:28 2016 -0800

    VMware: Support for non-default port
    
    Currently the VMDK driver fails to connect to vCenter server
    if vCenter is configured to listen to any port other than the
    default port 443. This patch fixes it by adding support for a
    new config option 'vmware_host_port' which specifies the port
    number to connect to vCenter server.
    
    DocImpact
      Added config option 'vmware_host_port' which specifies the
      port number to connect to vCenter server.
    
    Change-Id: I71846cdc09bc1ff2a7e35d45aa7c639c468f1418
    Co-Authored-By: Johnson koil raj <johnson.raj@xxxxxx>
    Closes-Bug: #1387074


** Changed in: cinder
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1387074

Title:
  VMware: Failed to launch instance if vCenter is configured to listen
  to any port other than 443

Status in Cinder:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  When a vCenter is configured to listen to any port other the default
  443. During instance launch the driver fails to make connection to
  vCenter when performing the glance image copy to the datastore.

  
  2014-10-29 20:03:25.535 ERROR oslo.vmware.api [-] Task: (returnval){
     value = "session[565de56e-2576-69ae-ae5f-50daafe6b90f]525ec5a1-a9f7-6c80-3c22-d78fb31ac069"
     _type = "Task"
   } failed with error: File [datastore1 (1)] 10.1.195.24_base/46e35b38-64f2-4cca-aa53-31407cf9a28e was not found.
  2014-10-29 20:03:25.535 ERROR oslo.vmware.common.loopingcall [-] in fixed duration looping call
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall Traceback (most recent call last):
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/oslo/vmware/common/loopingcall.py", line 76, in _inner
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall     self.f(*self.args, **self.kw)
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall   File "/usr/local/lib/python2.7/dist-packages/oslo/vmware/api.py", line 419, in _poll_task
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall     raise task_ex
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall FileNotFoundException: File [datastore1 (1)] 10.1.195.24_base/46e35b38-64f2-4cca-aa53-31407cf9a28e was not f
  2014-10-29 20:03:25.535 TRACE oslo.vmware.common.loopingcall 

  
  2014-10-29 19:21:16.448 ERROR nova.compute.manager [-] [instance: c2c69864-331a-4405-b589-4589d01cfd60] Instance failed to spawn
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60] Traceback (most recent call last):
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/compute/manager.py", line 2244, in _build_resources
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     yield resources
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/compute/manager.py", line 2114, in _build_and_run_instance
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     block_device_info=block_device_info)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/driver.py", line 488, in spawn
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     admin_password, network_info, block_device_info)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 484, in spawn
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     self._fetch_image_if_missing(context, vi)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 421, in _fetch_image_if_missing
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     image_fetch(context, vi, tmp_image_ds_loc)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/vmops.py", line 293, in _fetch_image_as_file
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     cookies=cookies)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/images.py", line 240, in fetch_image
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     host, dc_name, ds_name, cookies, file_path, file_size)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/opt/stack/nova/nova/virt/vmwareapi/read_write_util.py", line 131, in __init__
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     conn.endheaders()
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/usr/lib/python2.7/httplib.py", line 969, in endheaders
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     self._send_output(message_body)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/usr/lib/python2.7/httplib.py", line 829, in _send_output
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     self.send(msg)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/usr/lib/python2.7/httplib.py", line 791, in send
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     self.connect()
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/usr/lib/python2.7/httplib.py", line 1172, in connect
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     self.timeout, self.source_address)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]   File "/usr/local/lib/python2.7/dist-packages/eventlet/green/socket.py", line 60, in create_connection
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60]     raise error(msg)
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60] error: [Errno 111] ECONNREFUSED
  2014-10-29 19:21:16.448 TRACE nova.compute.manager [instance: c2c69864-331a-4405-b589-4589d01cfd60] 
  2014-10-29 19:21:16.449 AUDIT nova.compute.manager [req-622143c1-d783-48bc-80b6-829d5f07121d admin admin] [instance: c2c69864-331a-4405-b589-4589d01cfd60] Terminating instance

To manage notifications about this bug go to:
https://bugs.launchpad.net/cinder/+bug/1387074/+subscriptions
References

[Bug 1387074] [NEW] VMware: Failed to launch instance if vCenter is configured to listen to any port other than 443
From: Johnson koil raj, 2014-10-29