MSA 2050 is not registered
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Chris M |
Bug Description
In case of HP MSA 2050 storage, response data of login API is different from that of MSA 2040.
Please take look at the 'response-type'.
[MSA 2040]
# curl --insecure https:/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RESPONSE>
<OBJECT basetype="status" name="status" oid="1">
<PROPERTY name="response-
<PROPERTY name="response-
<PROPERTY name="response"
<PROPERTY name="return-
</OBJECT>
</RESPONSE>
[MSA 2050]
# curl --insecure https:/
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<RESPONSE VERSION="L100">
<OBJECT basetype="status" name="status" oid="1">
<PROPERTY name="response-
<PROPERTY name="response-
<PROPERTY name="response" type="string" size="180" draw="true" sort="nosort" display-
<PROPERTY name="return-code" type="sint32" size="15" draw="false" sort="nosort" display-
<PROPERTY name="component-id" type="string" size="80" draw="false" sort="nosort" display-
<PROPERTY name="time-stamp" type="string" size="25" draw="false" sort="datetime" display-
<PROPERTY name="time-
</OBJECT>
</RESPONSE>
Cinder volume tries to check login result using 'response-type' PROPERTY and compare it with 'success' so MSA 2050 is always failed to login.
Changed in xmms (Ubuntu): | |
assignee: | nobody → Jonghan (forhim-park) |
no longer affects: | xmms (Ubuntu) |
Changed in cinder: | |
assignee: | nobody → Jonghan (forhim-park) |
tags: | added: drivers hpe msa |
Fix proposed to branch: master /review. openstack. org/626104
Review: https:/