When we fixed the freeze mechanism we introduced a DB function called
``is_backend_frozen`` that is used to check in the DB whether a resource
(volume, group, etc.) is frozen or not.
The issue is that this function is not taking into consideration that in
some cases host/cluster_name may be comming with the pool information,
so the check will fail.
This patch fixes this by removing the pool information from host and
cluster_name parameters before doing the check in the DB.
Reviewed: https:/ /review. openstack. org/448147 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=66efc6c8d93 cc6fc9f533ec442 f238dfa5d0b132
Committed: https:/
Submitter: Jenkins
Branch: master
commit 66efc6c8d93cc6f c9f533ec442f238 dfa5d0b132
Author: Gorka Eguileor <email address hidden>
Date: Tue Mar 21 16:08:09 2017 +0100
Fix host check in is_backend_frozen
When we fixed the freeze mechanism we introduced a DB function called backend_ frozen` ` that is used to check in the DB whether a resource
``is_
(volume, group, etc.) is frozen or not.
The issue is that this function is not taking into consideration that in
some cases host/cluster_name may be comming with the pool information,
so the check will fail.
This patch fixes this by removing the pool information from host and
cluster_name parameters before doing the check in the DB.
TrivialFix
Change-Id: Ie776adf9e746cf 4cb7a2856d64d0b 94423149b8d
Closes-Bug: #1616974