Cinder IBM SVC Driver Timeout
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Won't Fix
|
Medium
|
IBM Storage |
Bug Description
We are using IBM Storwize SVC with iscsi on Mitaka
.
We encountered that the driver needs a long time at the function get_host_
We can reproduce this problem the following way:
1. Use heat template with single instance and empty additional volume which gets attached
2. Create multiple stacks by a script
If we for example did create 8 Stacks/Instances only about 4 get successfully created. The others are reaching a timeout in nova for attaching the volume (waiting for cinder).
Here a part of the logfile, to see it needs a long time:
2016-09-15 09:19:50.523 4801 cinder.
2016-09-15 09:20:05.433 4801 cinder.
2016-09-15 09:20:13.403 4801 cinder.
2016-09-15 09:20:28.119 4801 cinder.
2016-09-15 09:20:29.889 4801 cinder.
2016-09-15 09:20:44.889 4801 cinder.
Our workaround is a patch (see attachment). I tested it in our environment on Mitaka. As an alternative the rpc_timeout could be changed on nova and cinder.
Because the hostname of the nova-compute node is known in this function and if a host get's created on the storage it will get named by its hostname we could first limit the search to this hostname.
I can attach more logfiles if needed :-)
tags: | added: ibm |
Changed in cinder: | |
assignee: | nobody → IBM Storage (ibm-storage) |
Changed in cinder: | |
status: | New → Won't Fix |
My patch throws a error if the host does not exist on the storage system. lshost( host=connector[ 'host'] .partition( '.')[0] )" should maybe be wrapped with a try catch.
The line "resp = self.ssh.