commit 085b241de9e4098cdd92c46e9b57c5f24956db8e
Author: Csaba Henk <email address hidden>
Date: Sat Oct 10 01:23:11 2015 +0200
glusterfs/volume layout: fix incorrect usage of export_location
Actually, all uses of export_location are incorrect -- from the
layout code's point of view, export_location is an arbitrary
opaque value, obtained from self.driver._setup_via_manager with
which the only legit action is to return it from create_share*.
That we use export_location as dict key in ensure_share is just
a pre-layout relict that survived by the virtue of remaining
unnoticed. Now the referred bug forced it out of the dark.
Change-Id: I965dae99486002f00145daff0cd2a848777b5b81
Partial-Bug: #1501670
(cherry picked from commit e91632b6e2ff34d9bf0be52f6ac7d5d2a7520245)
Reviewed: https:/ /review. openstack. org/249999 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=085b241de9e 4098cdd92c46e9b 57c5f24956db8e
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit 085b241de9e4098 cdd92c46e9b57c5 f24956db8e
Author: Csaba Henk <email address hidden>
Date: Sat Oct 10 01:23:11 2015 +0200
glusterfs/ volume layout: fix incorrect usage of export_location
Actually, all uses of export_location are incorrect -- from the _setup_ via_manager with
layout code's point of view, export_location is an arbitrary
opaque value, obtained from self.driver.
which the only legit action is to return it from create_share*.
That we use export_location as dict key in ensure_share is just
a pre-layout relict that survived by the virtue of remaining
unnoticed. Now the referred bug forced it out of the dark.
Change-Id: I965dae99486002 f00145daff0cd2a 848777b5b81 9bf0be52f6ac7d5 d2a7520245)
Partial-Bug: #1501670
(cherry picked from commit e91632b6e2ff34d