Description of problem:
Manila's scheduler evaluator uses the pyparsing library, which isn't listed as an RPM dependency.
Version-Release number of selected component (if applicable):
Eric, I notice that the cinder spec has 'BuildRequires: pyparsing' in addition
to 'Requires: pyparsing'. Is the first also needed? How do I know which
of the requirements are also build requirements?
(In reply to Tom Barron from comment #1)
This is just for Cinder's sample config file generation at build time. I believe Manila's config file generation works a bit differently, so adding it only to Requires: is probably sufficient.
proposed backport of change to RDO newton-rdo branch to match this change as well.
Deployed to overcloud with recent puddle. We have:
# yum list installed | grep python-manila.noarch
python-manila.noarch 1:3.0.0-5.el7ost @rhos-10.0-puddle
# yum deplist python-manila | grep pyparsing
dependency: pyparsing >= 2.0.1
provider: pyparsing.noarch 2.0.3-1.el7ost
Since this was fixed in 3.0.0-4 and we see the dependency with 3.0.0-5 I think we're OK.
Looks good to me! Thanks for doing this, Tom!
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.