Bug 1485056 - fence_vmware_soap - Unable to connect/login to fencing device
Summary: fence_vmware_soap - Unable to connect/login to fencing device
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: fence-agents
Version: 27
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Marek Grac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1545706
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-24 22:36 UTC by maverick.pt
Modified: 2018-02-26 16:53 UTC (History)
4 users (show)

Fixed In Version: fence-agents-4.1.0-1.fc27 fence-agents-4.1.1-1.fc27
Clone Of:
Environment:
Last Closed: 2018-02-26 16:53:12 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description maverick.pt 2017-08-24 22:36:09 UTC
Hi,

fence_vmware_soap isn't working at least on F25 and F26:

fence_vmware_soap -a 192.168.1.18 -l root -p xxxxxxxx -z --ssl-insecure -o list
Unable to connect/login to fencing device

------------------

python fence_vmware_soap-wrapper.py -a 192.168.1.18 -l root -p xxxxxxxxx -z --ssl-insecure -o list
The fencing agent "fence_vmware_soap" was found: /usr/sbin/fence_vmware_soap.
Removing the file: /tmp/fence_vmware_soap-debug.txt
Executing /usr/sbin/fence_vmware_soap with suds debugging enabled.
opening (https://192.168.1.18:443/sdk/vimService.wsdl)
Unable to connect/login to fencing device

cat /tmp/fence_vmware_soap-debug.txt
2017-08-24 23:33:17,632 DEBUG opening (https://192.168.0.8:443/sdk/vimService.wsdl)
2017-08-24 23:33:17,674 ERROR Unable to connect/login to fencing device


I tried for example on CentOS 6.9 and CentOS 7.3 and works.

Comment 1 Marek Grac 2017-08-25 08:12:53 UTC
Which version of python do you run?

centos6 and 7 use python2
fedora uses python3

but I'm not sure where your python points. It looks like it may be issue in:
* python2/python3 issues
* different version of python-suds

Comment 2 maverick.pt 2017-08-25 09:11:48 UTC
Fedora 25 and 26 is reporting 2.7.13:

python --version
Python 2.7.13

CentOS 6:

python --version
Python 2.6.6

CentOS 7:

python --version
Python 2.7.5

Comment 3 maverick.pt 2017-08-25 14:36:23 UTC
Ha, fence_vmware_soap itself calls directly python3 in F25 and F26:

cat /usr/sbin/fence_vmware_soap | grep python
#!/usr/bin/python3 -tt


I tried to change to python2 but problem persists.

Comment 4 Marek Grac 2017-09-01 10:10:28 UTC
@mvrk:

yes, it is compiled with python3 but if you run it with 'python script-name' it is ignored and interpreter that you have specified is used.

The only thing that is different between RHEL and Fedora in our case is python-suds package. 

Can you connect to https://192.168.1.18:443/sdk/vimService.wsdl using curl ?

Comment 5 maverick.pt 2017-09-01 10:38:22 UTC
curl --insecure https://192.168.1.18:443/sdk/vimService.wsdl

<?xml version="1.0" encoding="UTF-8" ?>
<!--
   Copyright 2005-2016 VMware, Inc.  All rights reserved.
-->
<definitions targetNamespace="urn:vim25Service"
   xmlns="http://schemas.xmlsoap.org/wsdl/"
   xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
   xmlns:interface="urn:vim25"
>
   <import location="vim.wsdl" namespace="urn:vim25" />
   <service name="VimService">
      <port binding="interface:VimBinding" name="VimPort">
         <soap:address location="https://localhost/sdk/vimService" />
      </port>
   </service>
</definitions>

Comment 6 Miroslav Lisik 2017-09-07 16:53:36 UTC
Hi,

which version of vsphere/ESXi do you have?

Comment 7 maverick.pt 2017-09-07 18:10:08 UTC
ESXi 6.0 U2 / vCenter Server Appliance 6.0 U2

Comment 8 maverick.pt 2017-12-17 12:23:28 UTC
Just upgraded to F27, and problem persists.

Comment 9 Oyvind Albrigtsen 2018-01-11 12:45:44 UTC
https://github.com/ClusterLabs/fence-agents/pull/119

Comment 10 Fedora Update System 2018-02-09 14:40:39 UTC
fence-agents-4.1.0-2.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-3a175e2785

Comment 11 Fedora Update System 2018-02-13 07:58:19 UTC
fence-agents-4.1.0-2.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-3a175e2785

Comment 12 maverick.pt 2018-02-13 20:01:58 UTC
Now connects, but can't get list of vms or get status:

fence_vmware_soap -a xxx.xxx.xxx.xxx -l Administrator -p xxx --ssl-insecure -o list
2018-02-13 21:01:14,575 ERROR: Failed: Unable to obtain correct plug status or plug is not available


fence_vmware_soap -a xxx.xxx.xxx.xxx -l Administrator -p xxx --ssl-insecure -n 420e3d72-4df5-3ccf-c9a2-60cbdcbaf2e9 -o status
2018-02-13 21:00:00,536 ERROR: Failed: Unable to obtain correct plug status or plug is not available

I tried with ESXi host and with vCenter.

Comment 13 Oyvind Albrigtsen 2018-02-15 11:19:06 UTC
This is a problem with the Python 3 version of the suds library, so I'll make a bz to have them fix that, and use Python 2 until it's fixed.

You should be able to use the new fence_vmware_rest (which should also be more efficient than the SOAP version) or fence_vmware_vcloud.

Comment 14 Fedora Update System 2018-02-15 15:35:36 UTC
fence-agents-4.1.1-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-700f106cd5

Comment 15 Fedora Update System 2018-02-16 16:27:23 UTC
fence-agents-4.1.1-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-700f106cd5

Comment 16 Fedora Update System 2018-02-26 16:53:12 UTC
fence-agents-4.1.1-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.