Description of problem:
When adding a STONITH device like this,

  pcs stonith create stonith_tux2 fence_vmware_soap ipaddr=192.0.2.70 \
  login=pacemaker passwd=TuxLovesFish ssl=1 ssl_insecure=1 \
  port=4229DFFE-1ADD-2967-15D6-72574A46EFD2 action=reboot \
  pcmk_host_list=tux2.example.net op monitor interval=60s

where I explicitly specify "ssl_insecure=1" as a parameter (like stated in
the man page of fence_vmware_soap(1)), then I do not want to be nagged every
monitor interval (aka every 60 seconds) in /var/log/messages like this:

Nov 10 18:30:12 tux1 stonith-ng[1224]: warning: fence_vmware_soap[7777] stderr: [ /usr/lib/python2.7/site-packages/urllib3/connectionpool.py:769: InsecureRequestWarning: Unverified HTTPS request is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.org/en/latest/security.html ]
Nov 10 18:30:12 tux1 stonith-ng[1224]: warning: fence_vmware_soap[7777] stderr: [   InsecureRequestWarning) ]

I understand that the example above is insecure, but getting nagged is IMHO
absolutely fine when not having set "ssl_insecure=1" - but I do. Otherwise,
if you disagree about "ssl_insecure=1", please add a new option to silence
that as per choice of the administrator.

As per https://urllib3.readthedocs.org/en/latest/security.html these nagging
messages could be switched off or on program level, thus in the agent code.

Version-Release number of selected component (if applicable):
fence-agents-vmware-soap-4.0.11-47.el7.x86_64

How reproducible:
Everytime, see above.

Actual results:
Using fence_vmware_soap with ssl_insecure=1 still leads to security warnings.

Expected results:
No security warnings when ssl_insecure=1 is set for fence_vmware_soap.