DRBD: restarting DRBDmanage or DBus fail one call
Bug #1420171 reported by
Philipp Marek
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
Fix Released
|
Undecided
|
Philipp Marek | ||
Bug Description
When the DRBDmanage daemon or DBus get restarted, the next call done from the DRBDmanage driver fails.
| Changed in cinder: | |
| assignee: | nobody → Philipp Marek (philipp-marek) |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cinder (master) | #1 |
| Changed in cinder: | |
| status: | In Progress → Fix Committed |
| Changed in cinder: | |
| milestone: | none → kilo-3 |
| status: | Fix Committed → Fix Released |
| Changed in cinder: | |
| milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1c061402a22e409
Author: Philipp Marek <email address hidden>
Date: Tue Feb 10 10:07:53 2015 +0100
DRBD: Use correct function object after DBus disconnect.
When the DRBDmanage daemon gets restarted in some way, the DBus
object used is no longer valid.
But it's not enough to get a new object; the function got invalid,
too, so it has to be fetched anew.
Closes-Bug: #1420171
Change-Id: Ie4734d8e3a1839