For a share type extra-spec to match a Boolean capability
(using CapabilitiesFilter), the current design requires
the extra-spec value to use the syntax '<is> True' instead
of just True or 'True'.
When normal humans put 'True' in there, they will find a logged message
from the scheduler saying True is not equal True.
This is because there is a mismatch between the the extra-spec value(string)
and the actual boolean reported.
Fixed the bug by using strutils boolean to string converter.
Reviewed: https:/ /review. openstack. org/270604 /git.openstack. org/cgit/ openstack/ manila/ commit/ ?id=37e8a4100da 10ad4d70e451bab 4f38e4735c4256
Committed: https:/
Submitter: Jenkins
Branch: master
commit 37e8a4100da10ad 4d70e451bab4f38 e4735c4256
Author: nidhimittalhada <email address hidden>
Date: Wed Jan 20 16:50:17 2016 +0530
extra-specs should work with string True/False
For a share type extra-spec to match a Boolean capability ter), the current design requires
(using CapabilitiesFil
the extra-spec value to use the syntax '<is> True' instead
of just True or 'True'.
When normal humans put 'True' in there, they will find a logged message
from the scheduler saying True is not equal True.
This is because there is a mismatch between the the extra-spec value(string)
and the actual boolean reported.
Fixed the bug by using strutils boolean to string converter.
Change-Id: I959906bc92a374 abc25625d012cfb ad8aaf11065
Closes-Bug: #1493971