Public bug reported:
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://192.168.111.22/api/login/539e12f63b693a9970a97b885e857f8b
success
0
28f958fd88fd6e2acd7201624f7f8a82
1
[MSA 2050]
# curl --insecure
https://107.250.209.17/api/login/539e12f63b693a9970a97b885e857f8b
Success
0
79ea8ac277e1a4491ec7f6e9e6c0431b
1
2018-12-14 06:31:33
1544769093
Cinder volume tries to check login result using 'response-type' PROPERTY
and compare it with 'success' so MSA 2050 is always failed to login.
** Affects: xmms (Ubuntu)
Importance: Undecided
Assignee: Jonghan (forhim-park)
Status: New
** Changed in: xmms (Ubuntu)
Assignee: (unassigned) => Jonghan (forhim-park)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1808968
Title:
MSA 2050 is not registered
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xmms/+bug/1808968/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
