Bug 1437130

Summary:	libstoragemgmt: support to plugin using ssl does not work
Product:	Red Hat Enterprise Linux 7	Reporter:	Bruno Goncalves <bgoncalv>
Component:	libstoragemgmt	Assignee:	Gris Ge <fge>
Status:	CLOSED ERRATA	QA Contact:	Bruno Goncalves <bgoncalv>
Severity:	unspecified	Docs Contact:	Ioanna Gkioka <igkioka>
Priority:	unspecified
Version:	7.4	CC:	bgoncalv, fge
Target Milestone:	rc	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	libstoragemgmt-1.4.0-3.el7	Doc Type:	Deprecated Functionality
Doc Text:	SSLv2 and SSLv3 to NetApp ONTAP are discontinued The SSLv2 and SSLv3 connection to the NetApp ONTAP storage array are no longer supported by the libstorageMgmt library. Users can contact NetApp to enable the Transport Layer Security (TLS) protocol.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 16:47:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1403142

Description Bruno Goncalves 2017-03-29 14:44:39 UTC

Description of problem:
Trying to list volumes using plugin with ssl returns error.

NETWORK_ERROR(142): <urlopen error [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:579)> 

Version-Release number of selected component (if applicable):
libstoragemgmt-1.4.0-2.el7.x86_64
python-2.7.5-55.el7.x86_64
openssl-1.0.2k-5.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.# lsmcli  -u "ontap+ssl://<NetApp array>" list --type VOLUMES
NETWORK_ERROR(142): <urlopen error [SSL: UNSUPPORTED_PROTOCOL] unsupported protocol (_ssl.c:579)>

Comment 4 Gris Ge 2017-03-30 10:53:48 UTC

Patch posted to upstream for review.

https://github.com/libstorage/libstoragemgmt/pull/263

Comment 9 Bruno Goncalves 2017-04-28 09:33:58 UTC

Tested libstoragemgmt-1.4.0-3.el7 and it passed in our regression test.

Comment 10 errata-xmlrpc 2017-08-01 16:47:29 UTC

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/RHEA-2017:1976