solidfire: update_cluster_status() need better error handling for connectivity issues
Bug #1398877 reported by
Huang Zhiteng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
John Griffith |
Bug Description
If there is issue for solidfire driver to talk to the backend, get_volume_stats() would ignore any exception and report whatever old stats it has to scheduler. But the problem is, if there is no old data, i.e. self.cluster_stats is a empty dict, it would cause trouble in scheduler. Although that is a bug in scheduler too, I think it's better SF driver report mandatory stats with all zeroed value instead of an empty dict.
Changed in cinder: | |
assignee: | nobody → John Griffith (john-griffith) |
milestone: | none → mitaka-1 |
Changed in cinder: | |
milestone: | newton-rc1 → ocata-1 |
To post a comment you must log in.
Seems reasonable, I intentionally don't fail and kill the driver in the case of lost communications, but I would agree that we either shouldn't report the last know stats (zero them out) or even better we should probably add an "available" field to the stats that the scheduler can then check and ignore everything else if False.