+++ This bug was initially created as a clone of Bug #1170716 +++ Description of problem: when deployed "lonely" on a node, openstack-cinder does not pull in python-oslo-db resulting in a trace when cinder-volume starts: cinder-volume[2048]: Traceback (most recent call last): cinder-volume[2048]: File "/usr/bin/cinder-volume", line 52, in <module> cinder-volume[2048]: from cinder import service cinder-volume[2048]: File "/usr/lib/python2.7/site-packages/cinder/service.py", line 32, in <module> cinder-volume[2048]: from cinder import db cinder-volume[2048]: File "/usr/lib/python2.7/site-packages/cinder/db/__init__.py", line 20, in <module> cinder-volume[2048]: from cinder.db.api import * # noqa cinder-volume[2048]: File "/usr/lib/python2.7/site-packages/cinder/db/api.py", line 45, in <module> cinder-volume[2048]: from oslo.db import concurrency as db_concurrency cinder-volume[2048]: ImportError: No module named db Version-Release number of selected component (if applicable): openstack-cinder-2014.2-1.el7ost.noarch
Is this fixed in current packages?
*** Bug 1152350 has been marked as a duplicate of this bug. ***
Yes, it's pulled in by python-cinder