rootwrap default config has uppercase sections

Bug #1195781 reported by Mate Lakat
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Low
Mate Lakat

Bug Description

If you are using devstack to deploy neutron, agent will fail to start:

2013-06-28 15:26:53.004 29285 DEBUG quantum.agent.linux.utils [-]
Command: ['/opt/stack/quantum/bin/quantum-rootwrap-xen-dom0', '/etc/quantum/rootwrap.conf', 'ip', '-o', 'link', 'show', 'xapi1']
Exit code: 96
Stdout: ''
Stderr: 'Traceback (most recent call last):\n File "/opt/stack/quantum/bin/quantum-rootwrap-xen-dom0", line 102, in run_command\n session = XenAPI.Session(url)\n File "/usr/local/lib/python2.7/dist-packages/XenAPI.py", line 114, in __init__\n verbose, allow_none)\n File "/usr/lib/python2.7/xmlrpclib.py", line 1549, in __init__\n raise IOError, "unsupported XML-RPC protocol"\nIOError: unsupported XML-RPC protocol\n' execute /opt/stack/quantum/quantum/agent/linux/utils.py:59
2013-06-28 15:26:53.005 29285 ERROR quantum.plugins.openvswitch.agent.ovs_quantum_agent [-] Bridge xapi1 for physical network physnet1 does not exist. Agent terminated!

Trying to run the rootwrap command:

stack@DevStackOSDomU:~/quantum$ /opt/stack/quantum/bin/quantum-rootwrap-xen-dom0 /etc/quantum/rootwrap.conf ip -o link show xapi1
Traceback (most recent call last):
  File "/opt/stack/quantum/bin/quantum-rootwrap-xen-dom0", line 102, in run_command
    session = XenAPI.Session(url)
  File "/usr/local/lib/python2.7/dist-packages/XenAPI.py", line 114, in __init__
    verbose, allow_none)
  File "/usr/lib/python2.7/xmlrpclib.py", line 1549, in __init__
    raise IOError, "unsupported XML-RPC protocol"
IOError: unsupported XML-RPC protocol

Looking at the rootwrap config file, the problem becomes obvious:

$ cat /etc/quantum/rootwrap.conf
[DEFAULT]
# List of directories to load filter definitions from (separated by ',').
# These directories MUST all be only writeable by root !
filters_path=/etc/quantum/rootwrap.d

# List of directories to search executables in, in case filters do not
# explicitely specify a full path (separated by ',')
# If not specified, defaults to system PATH environment variable.
# These directories MUST all be only writeable by root !
exec_dirs=/sbin,/usr/sbin,/bin,/usr/bin

[XENAPI]
# XenAPI configuration is only required by the L2 agent if it is to
# target a XenServer/XCP compute host's dom0.
xenapi_connection_url=<None>
xenapi_connection_username=root
xenapi_connection_password=<None>

[xenapi]
xenapi_connection_password = stg
xenapi_connection_username = root

And the rootwrap is searching for the config with capital letters.

Tags: xenserver
Mate Lakat (mate-lakat)
description: updated
Changed in neutron:
assignee: nobody → Mate Lakat (mate-lakat)
tags: added: xenserver
Mate Lakat (mate-lakat)
Changed in neutron:
status: New → In Progress
Changed in neutron:
importance: Undecided → Low
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to quantum (master)

Reviewed: https://review.openstack.org/34902
Committed: http://github.com/openstack/quantum/commit/8d0f8e1b992f41a3914030ed75d77bbecde5f924
Submitter: Jenkins
Branch: master

commit 8d0f8e1b992f41a3914030ed75d77bbecde5f924
Author: Mate Lakat <email address hidden>
Date: Fri Jun 28 16:22:04 2013 +0100

    dom0 rootwrap - case insensitive xenapi section

    As per change https://review.openstack.org/33429 the config sections
    became lowercase. This patch makes the quantum-rootwrap-xen-dom0
    rootwrap to be case insensitive for the xenapi section.

    This patch also changes the default config file to use a lowercase
    xenapi section.

    Fixes bug 1195781

    Change-Id: Ic24feb1a9ad6f8823745b1febd4a0edd54e73498

Changed in neutron:
status: In Progress → Fix Committed
Changed in neutron:
milestone: none → havana-2
Thierry Carrez (ttx)
Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: havana-2 → 2013.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.