Pure driver sometimes fails to terminate connection to host
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Patrick East | ||
Kilo |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Sometimes we can get into a state where a Purity host is deleted before we try and disconnect a volume from it. The result is an error message like:
2015-07-08 04:34:49.327 ERROR cinder.
[{"msg": "Host does not exist.", "ctx": "image-
2015-07-08 04:34:49.328 ERROR cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
2015-07-08 04:34:49.328 TRACE cinder.
If this happens while creating a volume from an image (ie when detaching from the cinder node) it will cause the volume to go into an error state... even though it is actually fine.
There should be some protection for this case in terminate_
Changed in cinder: | |
assignee: | nobody → Patrick East (patrick-east) |
Changed in cinder: | |
milestone: | none → liberty-2 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-2 → 7.0.0 |
Fix proposed to branch: master /review. openstack. org/201334
Review: https:/