[ 
https://issues.apache.org/jira/browse/LIBCLOUD-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13266391#comment-13266391
 ] 

Tomaz Muraus edited comment on LIBCLOUD-183 at 5/2/12 6:52 AM:
---------------------------------------------------------------

I tried applying latest patch (LIBCLOUD-183-vcloud_1_5-5.patch) to trunk, but 
it fails. Can you please have a look? As a consequence a bunch of tests also 
fails.

patching file libcloud/compute/drivers/vcloud.py
Hunk #11 FAILED at 802.
Hunk #12 succeeded at 946 (offset -1 lines).
Hunk #13 succeeded at 1128 (offset -1 lines).
Hunk #14 succeeded at 1191 (offset -1 lines).
Hunk #15 succeeded at 1280 (offset -1 lines).
1 out of 15 hunks FAILED -- saving rejects to file 
libcloud/compute/drivers/vcloud.py.rej
patching file 
test/compute/fixtures/vcloud_1_5/api_org_96726c78_4ae3_402f_b08b_7a78c6903d2a.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6a.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b.xml
patching file test/compute/fixtures/vcloud_1_5/api_vApp_vm_test.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vdc_3d9ae28c_1de9_4307_8107_9356ff8ba6d0.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_cpu.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_disks.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_memory.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_cpu.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_disks.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_memory.xml
patching file test/compute/test_vcloud.py
Reversed (or previously applied) patch detected!  Assume -R? [n]


-----

...
======================================================================
ERROR: test_list_nodes_response (test.compute.test_vcloud.VCloud_1_5_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/w/lc/trunk/test/compute/__init__.py", line 25, in 
test_list_nodes_response
    nodes = self.driver.list_nodes()
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 504, in list_nodes
    raise e
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 495, in list_nodes
    headers={'Content-Type': 'application/vnd.vmware.vcloud.vApp+xml'}
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 254, in request
    return super(VCloudConnection, self).request(*args, **kwargs)
  File "/w/lc/trunk/libcloud/common/base.py", line 562, in request
    headers=headers)
  File "/w/lc/trunk/test/__init__.py", line 161, in request
    meth = getattr(self, meth_name)
AttributeError: 'VCloud_1_5_MockHttp' object has no attribute 
'_api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b'

======================================================================
ERROR: test_reboot_node (test.compute.test_vcloud.VCloud_1_5_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/w/lc/trunk/test/compute/test_vcloud.py", line 136, in test_reboot_node
    node = self.driver.list_nodes()[0]
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 504, in list_nodes
    raise e
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 495, in list_nodes
    headers={'Content-Type': 'application/vnd.vmware.vcloud.vApp+xml'}
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 254, in request
    return super(VCloudConnection, self).request(*args, **kwargs)
  File "/w/lc/trunk/libcloud/common/base.py", line 562, in request
    headers=headers)
  File "/w/lc/trunk/test/__init__.py", line 161, in request
    meth = getattr(self, meth_name)
AttributeError: 'VCloud_1_5_MockHttp' object has no attribute 
'_api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b'

======================================================================
ERROR: test_reboot_node_response (test.compute.test_vcloud.VCloud_1_5_Tests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/w/lc/trunk/test/compute/__init__.py", line 75, in 
test_reboot_node_response
    node = self.driver.list_nodes()[0]
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 504, in list_nodes
    raise e
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 495, in list_nodes
    headers={'Content-Type': 'application/vnd.vmware.vcloud.vApp+xml'}
  File "/w/lc/trunk/libcloud/compute/drivers/vcloud.py", line 254, in request
    return super(VCloudConnection, self).request(*args, **kwargs)
  File "/w/lc/trunk/libcloud/common/base.py", line 562, in request
    headers=headers)
  File "/w/lc/trunk/test/__init__.py", line 161, in request
    meth = getattr(self, meth_name)
AttributeError: 'VCloud_1_5_MockHttp' object has no attribute 
'_api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b'
...
                
      was (Author: kami):
    I tried applying latest patch (LIBCLOUD-183-vcloud_1_5-5.patch) to trunk, 
but it fails. Can you please have a look? As a consequence a bunch of tests 
also fails.

patching file libcloud/compute/drivers/vcloud.py
Hunk #11 FAILED at 802.
Hunk #12 succeeded at 946 (offset -1 lines).
Hunk #13 succeeded at 1128 (offset -1 lines).
Hunk #14 succeeded at 1191 (offset -1 lines).
Hunk #15 succeeded at 1280 (offset -1 lines).
1 out of 15 hunks FAILED -- saving rejects to file 
libcloud/compute/drivers/vcloud.py.rej
patching file 
test/compute/fixtures/vcloud_1_5/api_org_96726c78_4ae3_402f_b08b_7a78c6903d2a.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6a.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vApp_vapp_8c57a5b6_e61b_48ca_8a78_3b70ee65ef6b.xml
patching file test/compute/fixtures/vcloud_1_5/api_vApp_vm_test.xml
patching file 
test/compute/fixtures/vcloud_1_5/api_vdc_3d9ae28c_1de9_4307_8107_9356ff8ba6d0.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_cpu.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_disks.xml
patching file 
test/compute/fixtures/vcloud_1_5/get_api_vApp_vm_test_virtualHardwareSection_memory.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_cpu.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_disks.xml
patching file 
test/compute/fixtures/vcloud_1_5/put_api_vApp_vm_test_virtualHardwareSection_memory.xml
patching file test/compute/test_vcloud.py
Reversed (or previously applied) patch detected!  Assume -R? [n]
                  
> Implement support for vCloud v1.5
> ---------------------------------
>
>                 Key: LIBCLOUD-183
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-183
>             Project: Libcloud
>          Issue Type: New Feature
>          Components: Compute
>    Affects Versions: 0.9.1
>            Reporter: Michal Galet
>         Attachments: LIBCLOUD-183-networks-typo.patch, 
> LIBCLOUD-183-vcloud_1_5-2.patch, LIBCLOUD-183-vcloud_1_5-3.patch, 
> LIBCLOUD-183-vcloud_1_5-4.patch, LIBCLOUD-183-vcloud_1_5-5.patch, 
> LIBCLOUD-183-vcloud_1_5.patch, create_node_ex_net.recommended.xml, 
> create_node_ex_net.test.txt
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
> The current version of libcloud has support only for vCloud v0.8 and is 
> incompatible with the recent version of vCloud v1.5. 
> It would be nice if the newer version was supported by libcloud: 
> http://communities.vmware.com/thread/302725

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to