Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2017:1874