Fixed version uploaded to trusty-proposed for SRU team review. ** Description changed:
- I'm currently trying to integrate an OpenStack testbed (based on - Icehouse nova-2014.1 , Ubuntu 14.04 standard packages) with VCenter. I - configured nova.conf http://docs.openstack.org/trunk/config- - reference/content/vmware.html: + [Impact] + Users of the Nova VMWare integration can't use the distro provided package. + + [Test Case] + sudo apt-get install nova-compute-vmware + (configure /etc/nova/nova.conf to point to a vsphere deployment) + error in original bug report + + [Regression potential] + The fix is to drop a distro patch which has all ready been dropped in Debian and utopic. + + [Original Bug Report] + I'm currently trying to integrate an OpenStack testbed (based on Icehouse nova-2014.1 , Ubuntu 14.04 standard packages) with VCenter. I configured nova.conf http://docs.openstack.org/trunk/config-reference/content/vmware.html: compute_driver=vmwareapi.VMwareVCDriver reserved_host_memory_mb=0 [vmware] host_ip=192.168.0.146 host_username=root host_password=<password_here> cluster_name=VCOS datastore_regex=qnap* Using the password I'm able to login to VCenter using vSphere Web Client, Cluster VCOS was created using DRS, and I also defined a port group br-int on the ESXi hosts in the cluster. Although OpenStack Nova using KVM works like a breeze on two other compute nodes, I constantly get error messages on the node running VMwareVCDriver in note- compute.log 2014-04-30 16:44:10.263 1383 ERROR suds.client [-] <?xml version="1.0" encoding="UTF-8"?> <SOAP-ENV:Envelope 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:RetrieveServiceContent> - <_this type="ServiceInstance">ServiceInstance</_this> - </ns0:RetrieveServiceContent> - </ns1:Body> + <ns1:Body> + <ns0:RetrieveServiceContent> + <_this type="ServiceInstance">ServiceInstance</_this> + </ns0:RetrieveServiceContent> + </ns1:Body> </SOAP-ENV:Envelope> 2014-04-30 16:44:10.265 1383 CRITICAL nova.virt.vmwareapi.driver [-] Unable to connect to server at 192.168.78.103, sleeping for 60 seconds 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver Traceback (most recent call last): 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 795, in _create_session 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver self.vim = self._get_vim_object() 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 784, in _get_vim_object 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver return vim.Vim(protocol=self._scheme, host=self._host_ip) 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 117, in __init__ 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver self._service_content = self.retrieve_service_content() 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 120, in retrieve_service_content 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver return self.RetrieveServiceContent("ServiceInstance") 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vim.py", line 196, in vim_request_handler 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver raise error_util.VimFaultException(fault_list, excep) 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver VimFaultException: Server raised fault: 'Element tag ns0:RetrieveServiceContent uses an undefined namespace prefix ns0 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver while parsing SOAP body 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver at line 1, column 224 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver while parsing SOAP envelope 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver at line 1, column 38 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver while parsing HTTP request before method was determined 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver at line 1, column 0' 2014-04-30 16:44:10.265 1383 TRACE nova.virt.vmwareapi.driver ...to me it seems like there is some problem with the SOAP message... ns0 is not defined as a namespace und <SOAP-ENV:Envelope>? I also tried a fresh install of the VCenter Appliance 5.1 and 5.5 without any luck. From the error message names above I cannot see any configuration etc. I might have missed? ** Also affects: suds (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: suds (Ubuntu Utopic) Importance: Undecided Status: New ** Changed in: suds (Ubuntu Utopic) Status: New => Fix Released ** Changed in: suds (Ubuntu Trusty) Status: New => In Progress ** Changed in: suds (Ubuntu Trusty) Importance: Undecided => High ** Changed in: suds (Ubuntu Trusty) Assignee: (unassigned) => James Page (james-page) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314674 Title: Unable to connect to VCenter 5.5 VimFaultException: Server raised fault: 'Element tag ns0:RetrieveServiceContent uses an undefined namespace prefix ns0 To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1314674/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
