Hello again,
Another problem I have is with Quantum. Same OS: Centos 6.3 + EPEL + EPEL-testing, selinux on, firewall on (as configured by anaconda), Openstack Folsom
I have skipped the nova-network section of http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL and used this instead: https://fedoraproject.org/wiki/QA:Testcase_Quantum_V2#Setup
Obviously I have replaced the systemctl commands with service and chkconfig. There is no openvswitch in EL6 yet so I used the one from here http://li.nux.ro/download/tmp/ (git 1.9.90). Except for the above there were some other issues I encountered with the instructions:
1. At the "Please check that the following are in /etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log:
2012-11-17 20:01:44 ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 171, in daemon_loop self.do_single_loop() File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 202, in do_single_loop target_ex_net_id = self._fetch_external_net_id() File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 183, in _fetch_external_net_id ex_nets = self.qclient.list_networks(**params)['networks'] File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 102, in with_params ret = self.function(instance, *args, **kwargs) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 244, in list_networks return self.get(self.networks_path, params=_params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 525, in get headers=headers, params=params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 510, in retry_request headers=headers, params=params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 447, in do_request resp, replybody = self.httpclient.do_request(action, method, body=body) File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 139, in do_request self.authenticate() File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 194, in authenticate content_type="application/json") File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 132, in _cs_request raise exceptions.Unauthorized(message=body) Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
And if I try to boot an (ami) image this is what I get:
/var/log/quantum/dhcp-agent.log:
012-11-17 20:04:02 INFO [quantum.agent.dhcp_agent] Synchronizing state 2012-11-17 20:04:02 ERROR [quantum.agent.dhcp_agent] Unable to enable dhcp. Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 91, in call_driver getattr(driver, action)() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 112, in enable self.spawn_process() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 258, in spawn_process utils.execute(cmd, self.root_helper) File "/usr/lib/python2.6/site-packages/quantum/agent/linux/utils.py", line 55, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'QUANTUM_RELAY_SOCKET_PATH=/var/lib/quantum/dhcp/lease_relay', 'QUANTUM_NETWORK_ID=ac677a39-f950-4a4c-a883-ed1244f122b0', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict-order', '--bind-interfaces', '--interface=tape7e12416-33', '--except-interface=lo', '--domain=openstacklocal', '--pid-file=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/pid', '--dhcp-hostsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/host', '--dhcp-optsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/opts', '--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update', '--leasefile-ro', '--dhcp-range=set:tag0,10.0.0.0,static,120s'] Exit code: 3 Stdout: '' Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
/var/log/quantum/server.log:
2012-11-17 20:01:32 WARNING [quantum.api.extensions] extension flavor not supported by plugin <quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 object at 0x27634d0> 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: extensions.pyc 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: extensions.py 2012-11-17 20:01:32 WARNING [quantum.api.extensions] Did not find expected name "Extensions" in /usr/lib/python2.6/site-packages/quantum/extensions/extensions.py 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: __init__.pyc 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: _quotav2_driver.py 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: __init__.py 2012-11-17 20:01:32 INFO [keystone.middleware.auth_token] Starting keystone auth_token middleware 2012-11-17 20:01:32 INFO [keystone.middleware.auth_token] Using /var/lib/quantum/keystone-signing as cache directory for signing certificate 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672
The only one that doesn't seem to be complaining is the agent:
/var/log/quantum/openvswitch-agent.log:
2012-11-17 19:49:26 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Assigning 1 as local vlan for net-id=ac677a39-f950-4a4c-a883-ed1244f122b0 2012-11-17 19:49:30 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c added 2012-11-17 19:49:30 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c updated. Details: {u'admin_state_up': True, u'network_id': u'ac677a39-f950-4a4c-a883-ed1244f122b0', u'segmentation_id': None, u'physical_network': None, u'device': u'bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c', u'port_id': u'bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c', u'network_type': u'local'} 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Agent out of sync with plugin! 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c added 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port e7e12416-339e-487f-9913-96cae4fd2cbe added 2012-11-17 20:01:33 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port e7e12416-339e-487f-9913-96cae4fd2cbe updated. Details: {u'admin_state_up': True, u'network_id': u'ac677a39-f950-4a4c-a883-ed1244f122b0', u'segmentation_id': None, u'physical_network': None, u'device': u'e7e12416-339e-487f-9913-96cae4fd2cbe', u'port_id': u'e7e12416-339e-487f-9913-96cae4fd2cbe', u'network_type': u'local'} 2012-11-17 20:01:33 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Assigning 1 as local vlan for net-id=ac677a39-f950-4a4c-a883-ed1244f122b0
And I end up with something like this:
[root@openstack ~]# nova list +--------------------------------------+--------+--------+----------+ | ID | Name | Status | Networks | +--------------------------------------+--------+--------+----------+ | b39fdaa8-80c6-4910-bae3-60c1b058eefa | qtest1 | ERROR | | +--------------------------------------+--------+--------+----------+
Any ideas?
Have a nice weekend everyone,
Lucian
Hi Lucian, Please see my inline comments. Thanks Gary
On 11/17/2012 10:08 PM, Nux! wrote:
Hello again,
Another problem I have is with Quantum. Same OS: Centos 6.3 + EPEL + EPEL-testing, selinux on, firewall on (as configured by anaconda), Openstack Folsom
I have skipped the nova-network section of http://fedoraproject.org/wiki/Getting_started_with_OpenStack_EPEL and used this instead: https://fedoraproject.org/wiki/QA:Testcase_Quantum_V2#Setup
Obviously I have replaced the systemctl commands with service and chkconfig. There is no openvswitch in EL6 yet so I used the one from here http://li.nux.ro/download/tmp/ (git 1.9.90). Except for the above there were some other issues I encountered with the instructions:
- At the "Please check that the following are in
/etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
Did you run the "sudo quantum-l3-setup --plugin openvswitch"?
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log:
2012-11-17 20:01:44 ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 171, in daemon_loop self.do_single_loop() File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 202, in do_single_loop target_ex_net_id = self._fetch_external_net_id() File "/usr/lib/python2.6/site-packages/quantum/agent/l3_agent.py", line 183, in _fetch_external_net_id ex_nets = self.qclient.list_networks(**params)['networks'] File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 102, in with_params ret = self.function(instance, *args, **kwargs) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 244, in list_networks return self.get(self.networks_path, params=_params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 525, in get headers=headers, params=params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 510, in retry_request headers=headers, params=params) File "/usr/lib/python2.6/site-packages/quantumclient/v2_0/client.py", line 447, in do_request resp, replybody = self.httpclient.do_request(action, method, body=body) File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 139, in do_request self.authenticate() File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 194, in authenticate content_type="application/json") File "/usr/lib/python2.6/site-packages/quantumclient/client.py", line 132, in _cs_request raise exceptions.Unauthorized(message=body) Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
This is due to the fact that keystone athentication is not working. A quick explanation - the l3 agent makes use of the quantum http client to interface with the quantum service. This requires keystone authentication. If this fails then the l3 agent will not be able to communicate with the service. Can you please do the following: 1. Check if the Quantum service is listening on port 9696? (netstat -an|grep 9696). Did you reboot after the installation? There is currently a know issue that the Quantum service hangs after reboot. If this is the case then you can just restart the quantum service (this has been fixed and will soon be packaged) 2. Can you please check the log files in /var/log/quantum. This may provide some additional information. 3. Can you please check the nova log files?
And if I try to boot an (ami) image this is what I get:
/var/log/quantum/dhcp-agent.log:
012-11-17 20:04:02 INFO [quantum.agent.dhcp_agent] Synchronizing state 2012-11-17 20:04:02 ERROR [quantum.agent.dhcp_agent] Unable to enable dhcp. Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 91, in call_driver getattr(driver, action)() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 112, in enable self.spawn_process() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 258, in spawn_process utils.execute(cmd, self.root_helper) File "/usr/lib/python2.6/site-packages/quantum/agent/linux/utils.py", line 55, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'QUANTUM_RELAY_SOCKET_PATH=/var/lib/quantum/dhcp/lease_relay', 'QUANTUM_NETWORK_ID=ac677a39-f950-4a4c-a883-ed1244f122b0', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict-order', '--bind-interfaces', '--interface=tape7e12416-33', '--except-interface=lo', '--domain=openstacklocal', '--pid-file=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/pid', '--dhcp-hostsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/host', '--dhcp-optsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/opts', '--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update', '--leasefile-ro', '--dhcp-range=set:tag0,10.0.0.0,static,120s'] Exit code: 3 Stdout: '' Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
Can you please provide details of "which quantum-dhcp-agent-dnsmasq-lease-update"?
/var/log/quantum/server.log:
2012-11-17 20:01:32 WARNING [quantum.api.extensions] extension flavor not supported by plugin <quantum.plugins.openvswitch.ovs_quantum_plugin.OVSQuantumPluginV2 object at 0x27634d0> 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: extensions.pyc 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: extensions.py 2012-11-17 20:01:32 WARNING [quantum.api.extensions] Did not find expected name "Extensions" in /usr/lib/python2.6/site-packages/quantum/extensions/extensions.py 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: __init__.pyc 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: _quotav2_driver.py 2012-11-17 20:01:32 INFO [quantum.api.extensions] Loading extension file: __init__.py 2012-11-17 20:01:32 INFO [keystone.middleware.auth_token] Starting keystone auth_token middleware 2012-11-17 20:01:32 INFO [keystone.middleware.auth_token] Using /var/lib/quantum/keystone-signing as cache directory for signing certificate 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672
The only one that doesn't seem to be complaining is the agent:
/var/log/quantum/openvswitch-agent.log:
2012-11-17 19:49:26 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Assigning 1 as local vlan for net-id=ac677a39-f950-4a4c-a883-ed1244f122b0 2012-11-17 19:49:30 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c added 2012-11-17 19:49:30 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c updated. Details: {u'admin_state_up': True, u'network_id': u'ac677a39-f950-4a4c-a883-ed1244f122b0', u'segmentation_id': None, u'physical_network': None, u'device': u'bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c', u'port_id': u'bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c', u'network_type': u'local'} 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Agent out of sync with plugin! 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port bbf3cdac-f1a9-4e90-b70e-a36b4204fb6c added 2012-11-17 20:01:32 INFO [quantum.openstack.common.rpc.impl_qpid] Connected to AMQP server on localhost:5672 2012-11-17 20:01:32 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port e7e12416-339e-487f-9913-96cae4fd2cbe added 2012-11-17 20:01:33 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Port e7e12416-339e-487f-9913-96cae4fd2cbe updated. Details: {u'admin_state_up': True, u'network_id': u'ac677a39-f950-4a4c-a883-ed1244f122b0', u'segmentation_id': None, u'physical_network': None, u'device': u'e7e12416-339e-487f-9913-96cae4fd2cbe', u'port_id': u'e7e12416-339e-487f-9913-96cae4fd2cbe', u'network_type': u'local'} 2012-11-17 20:01:33 INFO [quantum.plugins.openvswitch.agent.ovs_quantum_agent] Assigning 1 as local vlan for net-id=ac677a39-f950-4a4c-a883-ed1244f122b0
And I end up with something like this:
[root@openstack ~]# nova list +--------------------------------------+--------+--------+----------+ | ID | Name | Status | Networks | +--------------------------------------+--------+--------+----------+ | b39fdaa8-80c6-4910-bae3-60c1b058eefa | qtest1 | ERROR | | +--------------------------------------+--------+--------+----------+
Any ideas?
Can you please provide the nova.conf file.
Have a nice weekend everyone,
Lucian
On 18.11.2012 05:42, Gary Kotton wrote:
Hi Lucian,
Hello Gary,
- At the "Please check that the following are in
/etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
Did you run the "sudo quantum-l3-setup --plugin openvswitch"?
Yes!
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log: Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
This is due to the fact that keystone athentication is not working. A quick explanation - the l3 agent makes use of the quantum http client to interface with the quantum service. This requires keystone authentication. If this fails then the l3 agent will not be able to communicate with the service. Can you please do the following:
- Check if the Quantum service is listening on port 9696? (netstat
-an|grep 9696). Did you reboot after the installation? There is currently a know issue that the Quantum service hangs after reboot. If this is the case then you can just restart the quantum service (this has been fixed and will soon be packaged)
The port shows up in netstat and I have both rebooted and restarted the services several times.
- Can you please check the log files in /var/log/quantum. This may
provide some additional information. 3. Can you please check the nova log files?
I'll try to repeat my tests and check the log files for additional information.
And if I try to boot an (ami) image this is what I get:
/var/log/quantum/dhcp-agent.log:
012-11-17 20:04:02 INFO [quantum.agent.dhcp_agent] Synchronizing state 2012-11-17 20:04:02 ERROR [quantum.agent.dhcp_agent] Unable to enable dhcp. Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 91, in call_driver getattr(driver, action)() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 112, in enable self.spawn_process() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 258, in spawn_process utils.execute(cmd, self.root_helper) File "/usr/lib/python2.6/site-packages/quantum/agent/linux/utils.py", line 55, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'QUANTUM_RELAY_SOCKET_PATH=/var/lib/quantum/dhcp/lease_relay', 'QUANTUM_NETWORK_ID=ac677a39-f950-4a4c-a883-ed1244f122b0', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict-order', '--bind-interfaces', '--interface=tape7e12416-33', '--except-interface=lo', '--domain=openstacklocal', '--pid-file=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/pid', '--dhcp-hostsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/host', '--dhcp-optsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/opts', '--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update', '--leasefile-ro', '--dhcp-range=set:tag0,10.0.0.0,static,120s'] Exit code: 3 Stdout: '' Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
Can you please provide details of "which quantum-dhcp-agent-dnsmasq-lease-update"?
[root@openstack ~]# which quantum-dhcp-agent-dnsmasq-lease-update /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update [root@openstack ~]# rpm -qf /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update openstack-quantum-2012.2-2.el6.noarch
Can you please provide the nova.conf file.
Sure, http://fpaste.org/RUt2/
On 11/18/2012 10:16 AM, Nux! wrote:
On 18.11.2012 05:42, Gary Kotton wrote:
Hi Lucian,
Hello Gary,
- At the "Please check that the following are in
/etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
Did you run the "sudo quantum-l3-setup --plugin openvswitch"?
Yes!
This is odd as it should have updated the files.
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log: Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
This is due to the fact that keystone athentication is not working. A quick explanation - the l3 agent makes use of the quantum http client to interface with the quantum service. This requires keystone authentication. If this fails then the l3 agent will not be able to communicate with the service. Can you please do the following:
- Check if the Quantum service is listening on port 9696? (netstat
-an|grep 9696). Did you reboot after the installation? There is currently a know issue that the Quantum service hangs after reboot. If this is the case then you can just restart the quantum service (this has been fixed and will soon be packaged)
The port shows up in netstat and I have both rebooted and restarted the services several times.
- Can you please check the log files in /var/log/quantum. This may
provide some additional information. 3. Can you please check the nova log files?
I'll try to repeat my tests and check the log files for additional information.
And if I try to boot an (ami) image this is what I get:
/var/log/quantum/dhcp-agent.log:
012-11-17 20:04:02 INFO [quantum.agent.dhcp_agent] Synchronizing state 2012-11-17 20:04:02 ERROR [quantum.agent.dhcp_agent] Unable to enable dhcp. Traceback (most recent call last): File "/usr/lib/python2.6/site-packages/quantum/agent/dhcp_agent.py", line 91, in call_driver getattr(driver, action)() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 112, in enable self.spawn_process() File "/usr/lib/python2.6/site-packages/quantum/agent/linux/dhcp.py", line 258, in spawn_process utils.execute(cmd, self.root_helper) File "/usr/lib/python2.6/site-packages/quantum/agent/linux/utils.py", line 55, in execute raise RuntimeError(m) RuntimeError: Command: ['sudo', 'quantum-rootwrap', '/etc/quantum/rootwrap.conf', 'QUANTUM_RELAY_SOCKET_PATH=/var/lib/quantum/dhcp/lease_relay', 'QUANTUM_NETWORK_ID=ac677a39-f950-4a4c-a883-ed1244f122b0', 'dnsmasq', '--no-hosts', '--no-resolv', '--strict-order', '--bind-interfaces', '--interface=tape7e12416-33', '--except-interface=lo', '--domain=openstacklocal', '--pid-file=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/pid', '--dhcp-hostsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/host', '--dhcp-optsfile=/var/lib/quantum/dhcp/ac677a39-f950-4a4c-a883-ed1244f122b0/opts', '--dhcp-script=/usr/bin/quantum-dhcp-agent-dnsmasq-lease-update', '--leasefile-ro', '--dhcp-range=set:tag0,10.0.0.0,static,120s'] Exit code: 3 Stdout: '' Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
Can you please provide details of "which quantum-dhcp-agent-dnsmasq-lease-update"?
[root@openstack ~]# which quantum-dhcp-agent-dnsmasq-lease-update /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update [root@openstack ~]# rpm -qf /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update openstack-quantum-2012.2-2.el6.noarch
I need to check a few things here.
Can you please provide the nova.conf file.
Sure, http://fpaste.org/RUt2/
Can you please update to the following:
network_api_class = nova.network.quantumv2.api.API quantum_admin_username = quantum quantum_admin_password = servicepass quantum_admin_auth_url = http://127.0.0.1:35357/v2.0/ quantum_auth_strategy = keystone quantum_admin_tenant_name = service quantum_url = http://localhost:9696/ libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver
This may help.
Thanks Gary
On 18.11.2012 08:16, Nux! wrote:
On 18.11.2012 05:42, Gary Kotton wrote:
Hi Lucian,
Hello Gary,
- At the "Please check that the following are in
/etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
Did you run the "sudo quantum-l3-setup --plugin openvswitch"?
Yes!
Right, this one I solved by replacing servicepass with verybadpass in /etc/quantum/l3_agent.ini; so the section looks like this (wiki page should be updated): auth_url = http://localhost:35357/v2.0/ auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = verybadpass
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log: Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
This went away, too, apparently after fixing the file with the right credentials.
Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
This went away after `setenforce 0` so right now I'm running without selinux..
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Is there any fix coming? Running with these settings really makes me uncomfortable.
On 11/18/2012 10:57 AM, Nux! wrote:
On 18.11.2012 08:16, Nux! wrote:
On 18.11.2012 05:42, Gary Kotton wrote:
Hi Lucian,
Hello Gary,
- At the "Please check that the following are in
/etc/quantum/l3_agent.ini" section turns out that what I had in my ini file was this: "auth_url = http://127.0.0.1:5000/v2.0/ auth_region = RegionOne admin_tenant_name = admin admin_user = admin admin_password = verybadpass" I commented that out and replaced with the settings from instructions.
Did you run the "sudo quantum-l3-setup --plugin openvswitch"?
Yes!
Right, this one I solved by replacing servicepass with verybadpass in /etc/quantum/l3_agent.ini; so the section looks like this (wiki page should be updated): auth_url = http://localhost:35357/v2.0/ auth_region = RegionOne admin_tenant_name = service admin_user = quantum admin_password = verybadpass
All the quantum/openvswitch router/soubet/etc add worked (surprisingly). But now I see the following errors:
/var/log/quantum/l3-agent.log: Unauthorized: {"error": {"message": "Invalid user / password", "code": 401, "title": "Not Authorized"}}
This went away, too, apparently after fixing the file with the right credentials.
Stderr: '\ndnsmasq: cannot run lease-init script /usr/bin/quantum-dhcp-agent-dnsmasq-lease-update: No such file or directory\n'
This went away after `setenforce 0` so right now I'm running without selinux..
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Are you using "libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" in nova.conf?
Is there any fix coming? Running with these settings really makes me uncomfortable.
On 18.11.2012 09:01, Gary Kotton wrote:
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Are you using "libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" in nova.conf?
No, I'm using libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
On 11/18/2012 11:08 AM, Nux! wrote:
On 18.11.2012 09:01, Gary Kotton wrote:
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Are you using "libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" in nova.conf?
No, I'm using libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
Can you please update to the hybrid (I need to update the wiki). When the wiki was originally written the hybrid driver was not part of the folsom release. Since then it has been added.
On 18.11.2012 09:10, Gary Kotton wrote:
On 11/18/2012 11:08 AM, Nux! wrote:
On 18.11.2012 09:01, Gary Kotton wrote:
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Are you using "libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" in nova.conf?
No, I'm using libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
Can you please update to the hybrid (I need to update the wiki). When the wiki was originally written the hybrid driver was not part of the folsom release. Since then it has been added.
As far as I can understand the ovs driver would allow me to overcome the 4094 vlan limitation, I'm still struggling with understanding how the networking works. Would the hybrid driver allow me the same features?
On 11/18/2012 11:39 AM, Nux! wrote:
On 18.11.2012 09:10, Gary Kotton wrote:
On 11/18/2012 11:08 AM, Nux! wrote:
On 18.11.2012 09:01, Gary Kotton wrote:
I still could not launch an instance though, http://fpaste.org/rQcV/ The workaround is to do this http://wiki.libvirt.org/page/Guest_won%27t_start_-_warning:_could_not_open_/...
Are you using "libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtHybridOVSBridgeDriver" in nova.conf?
No, I'm using libvirt_vif_driver = nova.virt.libvirt.vif.LibvirtOpenVswitchDriver
Can you please update to the hybrid (I need to update the wiki). When the wiki was originally written the hybrid driver was not part of the folsom release. Since then it has been added.
As far as I can understand the ovs driver would allow me to overcome the 4094 vlan limitation, I'm still struggling with understanding how the networking works. Would the hybrid driver allow me the same features?
The hybrid driver is the OVS driver. It was created due to the fact that there were problems with Nova's security groups and the OVS driver that you had installed. There is still the VLAN limitation. But when one is using the OVS implementation one is able to define tunnels. This enables one to break out of the limit of the VLAN.
Hope that this little bit of information helps.
Thanks Gary
On 18.11.2012 11:30, Gary Kotton wrote:
The hybrid driver is the OVS driver. It was created due to the fact that there were problems with Nova's security groups and the OVS driver that you had installed. There is still the VLAN limitation. But when one is using the OVS implementation one is able to define tunnels. This enables one to break out of the limit of the VLAN.
Hope that this little bit of information helps.
Thanks Gary
Yes it does, Gary. Thanks a lot!
-
gkotton＠redhat.com -
nux＠li.nux.ro