3PAR_It can't be integrated with StoreServ 8400

[Jorge Luis]

Hello:

We are having problems with integrating the HPE 3Par StoreServ 8400 storage with Openstack/Cinder (Cinder version 11.1.2). The messages are the following:

1. Cinder connects to 3PAR correctly

REQ: curl -i https://3parIP:8080/api/v1/credentials -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '201'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Location': '/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b'
'Pragma': 'no-cache'
'Cache-Control': 'no-cache'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'
'Content-Type': 'application/json'}

 RESP BODY:{"key":"0-7e98fea1623c58abba88e85915022806-1f8ebd5b"}

2. Cinder tries to validate the "url or API context" /api/v1/system and gets a error 500 on the side of the 3PAR.

REQ: curl -i https://3ParIP:8080/api/v1/system -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '500'
'content-location': u'https://hp_3par_mxn6202k4s:8080/api/v1/system'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'
'Content-Type': 'application/json'}

 RESP BODY:{"code":1,"desc":"internal server error"}

3. Cinder disconnects

REQ: curl -i https://3ParIP:8080/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-7e98fea1623c58abba88e85915022806-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '200'
'content-location': u'https://hp_3par_mxn6202k4s:8080/api/v1/credentials/0-7e98fea1623c58abba88e85915022806-1f8ebd5b'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Pragma': 'no-cache'
'Cache-Control': 'no-cache'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

4. Cinder reconnects to 3PAR correctly to validate the CPG

REQ: curl -i https://3ParIP:8080/api/v1/credentials -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-3parclient"

RESP:{'status': '201'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Location': '/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b'
'Pragma': 'no-cache'
'Cache-Control': 'no-cache'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'
'Content-Type': 'application/json'}

5. Cinder makes the call to the CPG and 3PAR API says again error 500.

REQ: curl -i https://3ParIP:8080/api/v1/cpgs/CPG1 -X GET -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"
RESP:{'status': '500'
'content-location': u'https://3ParIP:8080/api/v1/cpgs/CPG1'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'
'Content-Type': 'application/json'}

RESP BODY:{"code":1,"desc":"internal server error"}

6. Cinder delete the session.

REQ: curl -i https://3ParIP:8080/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b DELETE -H "X-Hp3Par-Wsapi-Sessionkey: 0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b" -H "Accept: application/json" -H "User-Agent: python-3parclient"
_http_log_req /usr/lib/python2.7/site-packages/hpe3parclient/http.py:169

RESP:{'status': '200'
'content-location': u'https://3ParIP:8080/api/v1/credentials/0-c64b336cb93cc8075f7dd2619687a0a1-1f8ebd5b'
'Server': 'hp3par-wsapi'
'Connection': 'close'
'Pragma': 'no-cache'
'Cache-Control': 'no-cache'
'Date': 'Wed, 10 Oct 2018 05:29:03 GMT'}

We are using the following parameters in cinder:

Driver:
cinder.volume.drivers.hpe.hpe_3par_fc.HPE3PARFCDriver

Options:
hpe3par_api_url=https://3parIP:8080/api/v1
hpe3par_username=3parusername
hpe3par_password=3parpassword
hpe3par_cpg=CPG1
san_ip=3ParIP
san_login=3parusername
san_password=3parpassword
max_over_subscription_ratio=10.0
reserved_percentage=15
image_volume_cache_enabled = True
hpe3par_debug = true

3parusername is a user with the "edit" role.
The OS version of the 3par is 3.3.1 (MU2).

Also, I tried to configure with a HPE 3Par StoreServ 7400 (OS version: 3.2.2 MU6), with the same parameters in the cinder, and if it works.

I would like to know if they have reported this issue and if they have any idea what we could do solve it.

Thanks,

Jorge

[Sean McGinnis (sean-mcginnis)]

This should be addressed through calling HPE support.