Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1070755

Summary: openstack-neutron should require a version of iproute that includes netns.
Product: Red Hat OpenStack Reporter: Nir Magnezi <nmagnezi>
Component: openstack-neutronAssignee: Miguel Angel Ajo <majopela>
Status: CLOSED ERRATA QA Contact: Ofer Blaut <oblaut>
Severity: high Docs Contact:
Priority: high    
Version: 4.0CC: chrisw, lpeer, mlopes, nyechiel, oblaut, sclewis, sputhenp, yeylon
Target Milestone: z3Keywords: AutoVerified, ZStream
Target Release: 4.0   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: openstack-neutron-2013.2.2-5.el6ost Doc Type: Bug Fix
Doc Text:
Prior to this update, there was no requirement for 'iproute' in the openstack-neutron package. Consequently, under specific circumstances when openstack-neutron was installed and no yum update was run, iproute was kept on the original Red Hat Enterprise Linux version without netns support, preventing the neutron-agents from working correctly. This update adds a requirement for the Red Hat Enterprise Linux OpenStack Platform version of iproute, with the result that iproute is updated to the required version when openstack-neutron is installed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-25 19:26:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
patch to version dependency none

Description Nir Magnezi 2014-02-27 14:03:13 UTC
Description of problem:
=======================
I used foreman-installer[1] to deploy a Neutron Networker node.
post running the puppet agent, I noticed that the neutron-l3-agent failed to start. with the following error:

Stderr: 'Object "netns" is unknown, try "ip help".\n'

openstack-neutron should require a version of iproute that includes netns.

[1] foreman-installer-1.3.0-1.el6sat.noarch
    openstack-foreman-installer-1.0.4-1.el6ost.noarch


Version-Release number of selected component (if applicable):
=============================================================
openstack-neutron-openvswitch-2013.2.2-1.el6ost.noarch

How reproducible:
=================
Always

Steps to Reproduce:
===================
1. use foreman-installer to deploy a Neutron networker
2. check neutron-l3-agent status

Actual results:
===============

2014-02-27 14:57:17.553 20799 CRITICAL neutron [-] 
Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list']
Exit code: 255
Stdout: ''
Stderr: 'Object "netns" is unknown, try "ip help".\n'
2014-02-27 14:57:17.553 20799 TRACE neutron Traceback (most recent call last):
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/bin/neutron-l3-agent", line 10, in <module>
2014-02-27 14:57:17.553 20799 TRACE neutron     sys.exit(main())
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 857, in main
2014-02-27 14:57:17.553 20799 TRACE neutron     manager=manager)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/service.py", line 208, in create
2014-02-27 14:57:17.553 20799 TRACE neutron     periodic_fuzzy_delay=periodic_fuzzy_delay)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/service.py", line 141, in __init__
2014-02-27 14:57:17.553 20799 TRACE neutron     self.manager = manager_class(host=host, *args, **kwargs)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 778, in __init__
2014-02-27 14:57:17.553 20799 TRACE neutron     super(L3NATAgentWithStateReport, self).__init__(host=host, conf=conf)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 217, in __init__
2014-02-27 14:57:17.553 20799 TRACE neutron     self._destroy_router_namespaces(self.conf.router_id)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/l3_agent.py", line 249, in _destroy_router_namespaces
2014-02-27 14:57:17.553 20799 TRACE neutron     for ns in root_ip.get_namespaces(self.root_helper):
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line 183, in get_namespaces
2014-02-27 14:57:17.553 20799 TRACE neutron     output = cls._execute('', 'netns', ('list',), root_helper=root_helper)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/linux/ip_lib.py", line 81, in _execute
2014-02-27 14:57:17.553 20799 TRACE neutron     root_helper=root_helper)
2014-02-27 14:57:17.553 20799 TRACE neutron   File "/usr/lib/python2.6/site-packages/neutron/agent/linux/utils.py", line 75, in execute
2014-02-27 14:57:17.553 20799 TRACE neutron     raise RuntimeError(m)
2014-02-27 14:57:17.553 20799 TRACE neutron RuntimeError: 
2014-02-27 14:57:17.553 20799 TRACE neutron Command: ['sudo', 'neutron-rootwrap', '/etc/neutron/rootwrap.conf', 'ip', 'netns', 'list']
2014-02-27 14:57:17.553 20799 TRACE neutron Exit code: 255
2014-02-27 14:57:17.553 20799 TRACE neutron Stdout: ''
2014-02-27 14:57:17.553 20799 TRACE neutron Stderr: 'Object "netns" is unknown, try "ip help".\n'

Expected results:
=================
the iproute with netns should be installed and all neutron services (dhcp and l3 in our case) should be up and runnning.

Additional info:
================
to workaround the issue:
1. yum update iproute -y
2. service neutron-l3-agent restart

Comment 2 Miguel Angel Ajo 2014-03-10 20:56:07 UTC
Created attachment 872841 [details]
patch to version dependency

It seems that if you did a yum update after install, you get last version of everything (include iproute) automatically.

But foreman shouldn't be doing it after adding rhos repo.

Comment 7 errata-xmlrpc 2014-03-25 19:26:05 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/RHBA-2014-0334.html