Unable to create network using quantum

Asked by NarsingRao


I have strictly following the installation procedure for quantum as mentioned in the quide, I have created quantum user, binded to role and service in keystone and did the corresponding changes in nova.conf and quantum.conf file.

I am unable to create a network, when I am trying to create network , I am seein the following information from l3-agent.log file

2012-11-16 13:31:33 DEBUG [quantum.agent.linux.utils] Running command: ip -o link show br-ex
2012-11-16 13:31:33 DEBUG [quantum.agent.linux.utils]
Command: ['ip', '-o', 'link', 'show', 'br-ex']
Exit code: 0
Stdout: '9: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN \\ link/ether de:1b:73:c5:b8:47 brd ff:ff:ff:ff:ff:ff\n'
Stderr: ''
2012-11-16 13:31:33 DEBUG [quantumclient.client] REQ: curl -i http://localhost:9696/v2/v2.0/networks.json?router%3Aexternal=True -X GET -H "User-Agent: python-quantumclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: 7af5e08c1ebc4550b8c5192512df4c15"

2012-11-16 13:31:33 DEBUG [quantumclient.client] RESP:{'date': 'Fri, 16 Nov 2012 21:31:33 GMT', 'status': '404', 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8'}

2012-11-16 13:31:33 DEBUG [quantumclient.client] RESP BODY:404 Not Found

The resource could not be found.

2012-11-16 13:31:33 DEBUG [quantumclient.v2_0.client] Error message: 404 Not Found

The resource could not be found.

2012-11-16 13:31:33 ERROR [quantum.agent.l3_agent] Error running l3_nat daemon_loop
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 170, in daemon_loop
  File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 201, in do_single_loop
    target_ex_net_id = self._fetch_external_net_id()
  File "/usr/lib/python2.7/dist-packages/quantum/agent/l3_agent.py", line 182, in _fetch_external_net_id
    ex_nets = self.qclient.list_networks(**params)['networks']
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 102, in with_params
    ret = self.function(instance, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 244, in list_networks
    return self.get(self.networks_path, params=_params)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 525, in get
    headers=headers, params=params)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 510, in retry_request
    headers=headers, params=params)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 455, in do_request
    self._handle_fault_response(status_code, replybody)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 436, in _handle_fault_response
    exception_handler_v20(status_code, des_error_body)
  File "/usr/lib/python2.7/dist-packages/quantumclient/v2_0/client.py", line 82, in exception_handler_v20
QuantumClientException: 404 Not Found

The resource could not be found.

root@openstack:~# keystone user-list
| id | name | enabled | email |
| 0a6da5fe748c45d686709f69e5f84960 | nova | True | <email address hidden> |
| 55465c99d3874f80ae6dadb4c6156887 | quantum | True | <email address hidden> |
| 86e9e78c71c848a6a19036d833f7dd34 | cinder | True | <email address hidden> |
| a3950766714147c1bbc052c38f57167d | swift | True | <email address hidden> |
| cbe2210f4f0d4277ae0d2d3f6eda035c | admin | True | <email address hidden> |
| d67832e0755749a1bc98005b8124bd6b | glance | True | <email address hidden> |
root@openstack:~# keystone service-list
| id | name | type | description |
| 2c740ebf67a44b68bdbec25df20b5003 | keystone | identity | OpenStack Identity Service |
| 789088e0a6204c7f82b4010f6cc6584c | quantum | network | OpenStack Networking service |
| 9f7829ed13c945a39ea279a60d27a974 | ec2 | ec2 | EC2 Service |
| a32549955e2543ec9b15cbbe06ab3e03 | cinder | volume | Cinder Service |
| a7345a6b62404c9ab0ae5ce0da776f28 | volume | volume | OpenStack Volume Service |
| d118544e3ea4487bb9402e035934ce21 | nova | compute | OpenStack Compute Service |
| d69099b908e14a349f10edba9879135a | glance | image | OpenStack Image Service |
| e19b2f8e17db4fd19b2ac580eb28c8d2 | swift | object-store | OpenStack Storage Service |
root@openstack:~# quantum net-list
404 Not Found

The resource could not be found.


Can anyone please let me know what I am doing wrong here


Question information

English Edit question
neutron Edit question
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #1079893.

Revision history for this message
Tom Fifield (fifieldt) said :

This is a question, rather than a docbug, so should be asked as a Question in launchpad.

Revision history for this message
Edgar Magana (emagana) said :

It seems that any of the Quantum Services is not running, do you have the following processes running?
#ps -ef |grep quantum
python /opt/stack/quantum/bin/quantum-server --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
python /opt/stack/quantum/bin/quantum-openvswitch-agent --config-file /etc/quantum/quantum.conf --config-file /etc/quantum/plugins/openvswitch/ovs_quantum_plugin.ini
python /opt/stack/quantum/bin/quantum-dhcp-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/dhcp_agent.ini
python /opt/stack/quantum/bin/quantum-l3-agent --config-file /etc/quantum/quantum.conf --config-file=/etc/quantum/l3_agent.ini

Could you also verify in their respective logs is everything is ok.
I also recommend to install another host using devstack: http://wiki.openstack.org/QuantumDevstack
It will help you to verify all your configuration files.

Revision history for this message
dan wendlandt (danwent) said :

well, the fact that we are getting an HTTP 404 error code and not a "connection refused" implies that quantum is running (or at least, some server is running on the IP + port you are specifying at the quantum server address.

Can you post the logs for quantum-server, and the l3_agent.ini (probably in /etc/quantum) used for the agent?

Can you help with this problem?

Provide an answer of your own, or ask NarsingRao for more information if necessary.

To post a message you must log in.