Unfortunately EMC doesn't monitor the mailing lists well. I would recommend reaching out to Helen.Walsh@dell.com . She can get you in touch with the right person to help. Thanks! Jay On 4/15/2019 12:21 PM, hao wang wrote:
hi guys:
Now I was using unisphere 4.4 as cinder's backend with ipv6 address. But there is an exception when I try to start the cinder volume:
2019-04-15 17:14:25.832 25795 DEBUG storops.connection.client [req-b86ea626-dcd5-4d76-9186-4f2dc902f244 - - - - -] REQ URL: [GET] https://[2019:c:0:0:0:0:0:220]:443/api/types/basicSystemInfo?compact=True&fields=attributes.description,attributes.displayValue,attributes.initialValue,attributes.name,attributes.type,description,documentation,name,type, TIME: 0.019809961319, RESP CODE: 400 log_response /usr/local/lib/python2.7/site-packages/storops/connection/client.py:186 2019-04-15 17:14:25.833 25795 DEBUG storops.connection.client [req-b86ea626-dcd5-4d76-9186-4f2dc902f244 - - - - -] RESP BODY: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>400 Bad Request</title> </head><body> <h1>Bad Request</h1> <p>Your browser sent a request that this server could not understand.<br /> </p> </body></html> _debug_print_json /usr/local/lib/python2.7/site-packages/storops/connection/client.py:179
I have configured the ipv6 and ipv4 address in unisphere and it connected well with my cinder volume node. When I switched the unify driver to ipv4 san ip in cinder.conf, it worked well.... So I really didn't get where is wrong.
Could guys help me out here? thanks.