Bug 1036514 - neutron-server still references quantum rootwrap and fails to start
Summary: neutron-server still references quantum rootwrap and fails to start
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 4.0
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: rc
: 4.0
Assignee: Terry Wilson
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks: RHEL-OSP_Neutron_HA
TreeView+ depends on / blocked
 
Reported: 2013-12-02 08:12 UTC by Fabio Massimo Di Nitto
Modified: 2016-04-26 20:50 UTC (History)
7 users (show)

Fixed In Version: openstack-neutron-2013.2-11.el6ost
Doc Type: Bug Fix
Doc Text:
Cause: There were still references to quantum-rootwrap in the neutron config files. Consequence: Starting neutron could fail. Fix: Replace references to quantum-rootwrap with neutron-rootwrap Result: Starting neutron no longer fails
Clone Of:
Environment:
Last Closed: 2013-12-20 00:40:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 0 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC

Description Fabio Massimo Di Nitto 2013-12-02 08:12:20 UTC
This is a fresh install of neutron:

[root@rhos4-node5 ~]# rpm -q -f /etc/init.d/neutron-server 
openstack-neutron-2013.2-10.el6ost.noarch

try to start the service will return OK but service will fail later because it is looking quantum/rootwrap.conf by default.


In order to workaround the issue I had to do:

[root@rhos4-node6 ~(keystone_admin)]# cd /etc/
[root@rhos4-node6 etc(keystone_admin)]# mkdir quantum
[root@rhos4-node6 etc(keystone_admin)]# cp neutron/rootwrap.conf quantum/

echo "neutron ALL = (root) NOPASSWD: SETENV: /usr/bin/quantum-rootwrap" >> /etc/sudoers.d/neutron

Comment 6 errata-xmlrpc 2013-12-20 00:40:34 UTC
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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html


Note You need to log in before you can comment on or make changes to this bug.