Install and configure Cinder controller node in Installation Guide

[Bejoy C Alias]

After following the documented steps in the Cinder controller node installation, running [su -s /bin/sh -c "cinder-manage db sync" cinder] fails with error "ImportError: No module named oslo_policy". I had to manually install "python-oslo-policy" package to fix this. So the initial command "yum install openstack-cinder python-cinderclient" should be modified as "yum install openstack-cinder python-cinderclient python-oslo-policy" to include the missing package. (OR cinder packaging dependencies to be updated?)
-----------------------------------
Release: 0.1 on 2016-01-14 08:23
SHA: ab79de9486175687ee6205ccce4c8f7598c89032
Source: http://git.openstack.org/cgit/openstack/openstack-manuals/tree/doc/install-guide/source/cinder-controller-install.rst
URL: http://docs.openstack.org/liberty/install-guide-rdo/cinder-controller-install.html

[venkatamahesh (venkatamaheshkotha)]

Hi,
can you please add the log data which you got while you got error

[Bejoy C Alias (peeloos-i)]

This is the command window error message I got. And there is no other openstack log file created at this stage.

[root@centos ~]# su -s /bin/sh -c "cinder-manage db sync" cinder
Traceback (most recent call last):
  File "/bin/cinder-manage", line 6, in <module>
    from cinder.cmd.manage import main
  File "/usr/lib/python2.7/site-packages/cinder/cmd/manage.py", line 72, in <module>
    from cinder import context
  File "/usr/lib/python2.7/site-packages/cinder/context.py", line 29, in <module>
    from cinder import policy
  File "/usr/lib/python2.7/site-packages/cinder/policy.py", line 20, in <module>
    from oslo_policy import opts as policy_opts
ImportError: No module named oslo_policy

[venkatamahesh (venkatamaheshkotha)]

oslo.policy is there in requirements.txt file of openstack/cinder project. I think before the step " yum install ....." . we have to install requirements.txt by " pip install -r requirements.txt"

I think by this way we can't get error. Once check by doing this.

Thanks

[Bejoy C Alias (peeloos-i)]

I believe this has to be documented in the installation guide, if we have to first install these requirements packages? But are we supposed to do such an installation from requirements.txt file when I am simply installing the Cinder rpm file, and not doing any git clones etc.? [I dont see this as a step for any other services too].
I think the better option would be to just update the installation guide to include 'python-oslo-policy' to the package list where it is mentioned 'yum install openstack-cinder python-cinderclient'?

[Matt Kassawara (ionosphere80)]

Venkatamahesh,

We avoid using pip in the installation guide because mixing OpenStack distro packages and pip packages usually destroys the installation.

Bejoy,

Did you install other OpenStack services prior to cinder?

[Bejoy C Alias (peeloos-i)]

Hi Matt,
Nope, I did not install any other services in this node. This is my dedicated Cinder node, and this is the only openstack package I install to this node.
(I guess, if I used my other nodes I setup earlier, there were documented steps in the guide where I install this python-oslo-policy package. So this must have worked in that node. Since this is a dedicated node, and the document did not say this package requirement explicitly, I did not install this and got this error.)

[Matt Kassawara (ionosphere80)]

Potential packaging problem.

[James Page (james-page)]

python-cinder has a direct dependency on python-oslo.policy in the latest mitaka packages:

   python-oslo.policy (>= 0.5.0)

its possible this was missing in previous versions - which openstack release are you working with?

[James Page (james-page)]

Ditto in the liberty packaging (has python-oslo.policy (>= 0.5.0))

[Bejoy C Alias (peeloos-i)]

The issue is that this package did not get installed by default in a dedicated cinder node of Liberty and I had to manually install it. Running 'yum install openstack-cinder python-cinderclient' did not install 'python-oslo-policy'. It was installed manually since it gave the earlier mentioned error. This bug was raised to add this manual installation step to the installation document.

[Launchpad Janitor (janitor)]

[Expired for cinder (Ubuntu) because there has been no activity for 60 days.]