volume status should be updated after terminate_connection is done
Bug #1488857 reported by
Huang Zhiteng
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
Undecided
|
Huang Zhiteng |
Bug Description
Current volume API terminate_
Changed in cinder: | |
assignee: | nobody → Huang Zhiteng (zhiteng-huang) |
status: | New → In Progress |
Changed in cinder: | |
milestone: | none → liberty-3 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | liberty-3 → 7.0.0 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/199015 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=bf5d39277e7 c02df3994f3a501 9b60f7a64f9b07
Committed: https:/
Submitter: Jenkins
Branch: master
commit bf5d39277e7c02d f3994f3a5019b60 f7a64f9b07
Author: Zhiteng Huang <email address hidden>
Date: Tue Jul 7 16:31:32 2015 +0800
Update volume status AFTER terminate_ connection is done
Current volume API terminate_ connection( ) updates volume's status in connection( ). In cases connection( ), connection to make sure when volume is marked
DB before volume driver finishes terminate_
where volume driver needs some time complete terminate_
it means volume becomes 'available' before volume driver done cleaning
up. This fix changes the order of 'unreserve_volume' (updating DB)
and driver's terminate_
'available' the client has done cleaning connection.
Note that terminate_ connection volume RPC API is a synchronized call, connection API,
but volume manager/driver doesn't return any value to caller. What's
more, when volume API extension calls volume terminate_
it doesn't expect return values, so this change removes unnecessary
return values from volume API.
Closes-bug: #1488857
Change-Id: If79f7ce9a7d238 b41be4c6befa0f3 cac30ab06a3