543954dd05
It turns out that when you're in a context manager that has gotten the lock, attempting to set that lock to None will fail. It's also not the thing we actually want to do. What we WANT to do is reset the _service_ so that we'll ensure a new service object gets created. Change-Id: Ic39ef0418dcd5c0cbbe710ac1c31e58b744f56b5 |
||
---|---|---|
.. | ||
cache-in-use-volumes-c7fa8bb378106fe3.yaml | ||
cinderv2-norm-fix-037189c60b43089f.yaml | ||
create_server_network_fix-c4a56b31d2850a4b.yaml | ||
create_service_norm-319a97433d68fa6a.yaml | ||
create-stack-fix-12dbb59a48ac7442.yaml | ||
delete-obj-return-a3ecf0415b7a2989.yaml | ||
fip_timeout-035c4bb3ff92fa1f.yaml | ||
fix-list-networks-a592725df64c306e.yaml | ||
fix-update-domain-af47b066ac52eb7f.yaml | ||
get_object_api-968483adb016bce1.yaml | ||
grant-revoke-assignments-231d3f9596a1ae75.yaml | ||
list-role-assignments-keystone-v2-b127b12b4860f50c.yaml | ||
net_provider-dd64b697476b7094.yaml | ||
norm_role_assignments-a13f41768e62d40c.yaml | ||
service_enabled_flag-c917b305d3f2e8fd.yaml | ||
started-using-reno-242e2b0cd27f9480.yaml | ||
swift-upload-lock-d18f3d42b3a0719a.yaml |