Description of problem: RHEL 6.4 doesn't support namespace. L3 Agent will not work until router_id manually set and use_namespaces is set to False. This must be done on /etc/quantum/l3_agent.ini & quantum L3 agent must be restarted Upstream docs http://docs.openstack.org/folsom/openstack-network/admin/content/adv_cfg_l3_agent_namespace.html Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Shouldn't this be handled in the setup script for the agent if it won't work unless it is done?
(In reply to comment #2) > Shouldn't this be handled in the setup script for the agent if it won't work > unless it is done? Answered via the mailing list, the use_namespaces value is set correctly in the distribution specific configuration files. We will still need to cover router creation and the update to the router_id value.
The bug descripion is confusing. By default the RHOS packages have the namespaces disabled this is until we resolve bug: https://bugzilla.redhat.com/show_bug.cgi?id=869029 When namespaces are not used then the l3 agent needs the router_id as input. The sequence of events is as follows: 1. Create a router 2. Update the l3 agent configuration file with the router ID 3. restart the L3 agent I think that the intent of the bug is just to make sure that we have it documented that using the l3 agent requires the router id. This has limitations: 1. only one router id per l3 agent 2. we are unable to run l3 agents on the same nodes as dhcp agents
Description of problem: Please see https://review.openstack.org/21961 for a upstream documentation about this issue
*** Bug 911135 has been marked as a duplicate of this bug. ***
While that fixed the issue this bug covers I also noticed that this paragraph: " The node running quantum-l3-agent should not have an IP address manually configured on the NIC connected to the external network. Rather, you must have a range of IP addresses from the external network that can be used by OpenStack Network for routers that uplink to the external network. This range must be large enough to have an IP address for each router in the deployment, as well as each floating IP. " ...has little to do with the step being executed... $ sudo yum install -y openstack-quantum
tested on Revision 1.0-28
Added dependency on BZ 928815, which covers the limitation resulting from lack of network namespaces that results in the requirement to configure a router ID for the quantum-l3-agent.