Ask Your Question

jame's profile - activity

2015-12-10 00:10:19 -0500 received badge  Taxonomist
2014-11-20 04:34:16 -0500 received badge  Necromancer (source)
2014-11-15 11:19:04 -0500 received badge  Nice Answer (source)
2014-11-08 10:28:17 -0500 received badge  Necromancer (source)
2014-10-22 08:44:16 -0500 received badge  Nice Answer (source)
2014-10-11 03:41:41 -0500 received badge  Nice Question (source)
2014-06-17 22:03:17 -0500 commented answer neutron router-create demo-router results in 404

Yes that line service_plugins = router is there.

I found 1 missing parameter and 4 extra parameters on comparison using this style command comm -2 -3 <(sort neutron.conf) <(sort netron_bl.conf) but when I changed to match the file you referenced it didnt' fix the error.

2014-06-16 23:43:29 -0500 received badge  Famous Question (source)
2014-06-16 15:13:58 -0500 commented answer neutron router-create demo-router results in 404

It didn't work. I systematically cp ..ml2_conf.ini /etc/neutron and then retried and then restarted Neutron and retried and then cp ... ovs_neutron_plugin.ini and retry on first the Controller then Network then Compute node. Still get 404 error. Thanks for not giving up on this Boris.

2014-06-15 18:18:25 -0500 commented answer neutron router-create demo-router results in 404

Addin the agent_down_time and report_interval timeouts dont' change the error. If they are timeouts in seconds it doesn't seem to be a timeout issue since the error happens in a second or two.

netstat -antp | grep 5672 shows that rabbit is listening at 5672:

tcp6       0      0 :::5672                 :::*                    LISTEN      -
2014-06-15 18:10:22 -0500 commented answer neutron router-create demo-router results in 404

No problem at the same point in a 1 node DevStack following Sayalikuds instructions, but it doesn't lead me to a solution for 3 node install. It's good to have a config. to compare, but I want to test the Traing Environment instructions which are 3 node.

2014-06-14 17:26:55 -0500 received badge  Notable Question (source)
2014-06-13 17:01:59 -0500 received badge  Student (source)
2014-06-13 16:56:48 -0500 received badge  Popular Question (source)
2014-06-12 08:10:02 -0500 received badge  Commentator
2014-06-12 08:10:02 -0500 commented question neutron router-create demo-router results in 404

I added the reports to the main listing above.

2014-06-11 23:01:37 -0500 commented answer Mystery subnet

Deleteing the extra networks worked but I ran into another issue with create-router - seems a different one so I started a new topic: https://ask.openstack.org/en/question/32040/neutron-router-create-demo-router-results-in-404/

2014-06-11 22:55:12 -0500 asked a question neutron router-create demo-router results in 404

In a new installation of ICEhouse on Ubuntu 14.04 Host and VirtualBox VMs - 3 node configuration at the point where you create your router to connect external and tenant networks: I get this error:

neutron router-create route730tojOpStNet -v  # Its a descriptive router name but also fails if called demo-router

DEBUG: neutronclient.neutron.v2_0.router.CreateRouter get_data(Namespace(admin_state=True, columns=[], distributed=True, formatter='table', name=u'route730tojOpStNet', prefix='', request_format='json', tenant_id=None, variables=[]))
DEBUG: neutronclient.client 
REQ: curl -i http://controller:35357/v2.0/tokens -X POST -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-neutronclient" -d '{"auth": {"tenantName": "admin", "passwordCredentials": {"username": "admin", "password": "plato"}}}'

DEBUG: neutronclient.client RESP:{'status': '200', 'content-length': '4579', 'vary': 'X-Auth-Token', 'date': 'Thu, 12 Jun 2014 03:21:47 GMT', 'content-type': 'application/json', 'x-distribution': 'Ubuntu'} {"access": {"token": {"issued_at": "2014-06-12T03:21:47.231595", "expires": "2014-06-12T04:21:47Z", "id": ...

DEBUG: neutronclient.client 
REQ: curl -i http://controller:9696/v2.0/routers.json -X POST -H "X-Auth-Token: ...GbAGe7bU+iox5sfgo6qnsITZAFGGgfRZ7bXbezM+fWNZAHyBtc" -H "Content-Type: application/json" -H "Accept: application/json" -H "User-Agent: python-neutronclient" -d '{"router": {"name": "route730tojOpStNet", "admin_state_up": true}}'

DEBUG: neutronclient.client RESP:{'date': 'Thu, 12 Jun 2014 03:21:47 GMT', 'status': '404', 'content-length': '52', 'content-type': 'text/plain; charset=UTF-8', 'x-openstack-request-id': 'req-4e9e3585-b3a2-4514-9f55-a213441b960e'} 404 Not Found

The resource could not be found.

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 526, in run_subcommand
    return run_command(cmd, cmd_parser, sub_argv)
  File "/usr/lib/python2.7/dist-packages/neutronclient/shell.py", line 79, in run_command
    return cmd.run(known_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/common/command.py", line 34, in run
    return super(OpenStackCommand, self).run(parsed_args)
  File "/usr/lib/python2.7/dist-packages/cliff/display.py", line 84, in run
    column_names, data = self.take_action(parsed_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/common/command.py", line 40, in take_action
    return self.get_data(parsed_args)
  File "/usr/lib/python2.7/dist-packages/neutronclient/neutron/v2_0/__init__.py", line 419, in get_data
    data = obj_creator(body)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 111, in with_params
    ret = self.function(instance, *args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 396, in create_router
    return self.post(self.routers_path, body=body)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1241, in post
    headers=headers, params=params)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1164, in do_request
    self._handle_fault_response(status_code, replybody)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 1134, in _handle_fault_response
    exception_handler_v20(status_code, des_error_body)
  File "/usr/lib/python2.7/dist-packages/neutronclient/v2_0/client.py", line 91, in exception_handler_v20
    message=message)
NeutronClientException: 404 Not Found

The resource could not be found.

Note that the Keystone, Glance and nova installs as well as Neutron net-create and subnet-create seemed to be successful up to this point:

neutron net-list
+--------------------------------------+----------+------------------------------------------------------+
| id                                   | name     | subnets                                              |
+--------------------------------------+----------+------------------------------------------------------+
| 8b1df9b6-781c-4e3e-b81b-235b837256b8 | jOpStNet | 367c060c-7d7a-43a6-acd2-0dc8a50c56a4 192.168.50.0/24 |
| ad7ed8f3-9fea-44b6-b519-ff10851ee732 | 730Net   | 46745d51-1ded-46fb-b3ec-a6cac0258cc0 192.168.1.0/24  |
+--------------------------------------+----------+------------------------------------------------------+
keystone user-list
+----------------------------------+---------+---------+-------------------+
|                id                |   name  | enabled |       email       |
+----------------------------------+---------+---------+-------------------+
| 709d97386cba487885a5fb2fd83b4942 |  admin ...
(more)
2014-06-10 01:27:04 -0500 received badge  Necromancer (source)
2014-06-10 01:27:04 -0500 received badge  Teacher (source)
2014-06-09 09:46:45 -0500 commented answer ERROR [cinder.openstack.common.rpc.common] AMQP server on localhost:5672 is unreachable: Socket closed.

Just changing the password to guest (not password) worked for me - instantly with no service restart. It does not match my .conf settings for rabbit_password:

sudo rabbitmqctl change_password guest guest
2014-06-09 09:42:03 -0500 received badge  Enthusiast
2014-06-08 08:09:01 -0500 commented answer Mystery subnet

Detail on the order of events that resuted in this:

  1. Had difficulty with intitial run of neutron net-create ext-net.... due to bad Rabbit Password but finally solved
  2. Ran command above and same results.
  3. neutron net-list results in 4 entries only 1 which matches result of step 1
2014-06-07 15:50:31 -0500 answered a question Devstack ERROR neutron.openstack.common.rpc.common [-] AMQP server on ip:5672 is unreachable: [Errno 111] ECONNREFUSED.

Pretty good steps for debugging. Thanks. I learned a lot by following them. THe fix though was:

sudo rabbitmqctl change_password guest guest

No restart required.

2014-06-07 15:47:14 -0500 commented answer neutron-server cannot talk to AMQP

I have a 3 node setup - so a Controller Node and a network node and did extensive debugging and also changed the password to other than guest in the conf files. Issuing the command above instantly resolved. Seems the rabbit_password is hardcoded to guest no matter your conf files.

2014-06-06 21:10:05 -0500 received badge  Editor (source)
2014-06-06 21:07:14 -0500 answered a question cannot issue "nova-image list" or "glance image-list" after machine reload

At least for me this happened because of a bad endpoint create in step 10 on http://docs.openstack.org/icehouse/install-guide/install/apt/content/nova-controller.html. I was cutting and pasting from the instruction guide and missed the final s.

keystone endpoint-create \

--service-id=$(keystone service-list | awk '/ compute / {print $2}') \

--publicurl=http://controller:8774/v2/%(tenant_id)s \

--internalurl=http://controller:8774/v2/%(tenant_id)s \

--adminurl=http://controller:8774/v2/%(tenant_id) <---missing s

This creates a malformed endpoint which basically shuts down all communications with Keystone. See bug 1230279. Fixing it is kind of hard. I ended up deleting the endpoints using MYSQL delete. See instructions. Then I reentered the command above not malformed and restarted keystone.

2014-06-06 18:25:22 -0500 commented question cannot issue "nova-image list" or "glance image-list" after machine reload

I'm stuck at step 12 here: http://docs.openstack.org/icehouse/install-guide/install/apt/content/nova-controller.html (http://docs.openstack.org/icehouse/in...) with the same error for:

nova image-list

glance image-list

keystone user-list

though the last 2 worked fine before installing compute controller. Seems that something in

2014-06-05 19:36:37 -0500 answered a question glance image-create returns invalid credentials

For me I had to drop the Keystone user entry for glance and then recreate it and it's role and this fixed it. I suspect I did set the password wrong the first time, perhaps left the instruction manual password in there. Here's the commands I had to issue;

keystone user-list # to get the id

keystone user-delete cbadb6fff68a4165a09ba9db75cc850d

keystone user-create --name=glance --pass=password --email=me@gmail.com

keystone user-role-add --user=glance --tenant=service --role=admin

2014-06-05 19:33:54 -0500 commented answer Unable to add an image to glance service

For me I had to drop the Keystone user entry for glance and then recreate it and it's role and this fixed it. I suspect I did set the password wrong the first time, perhaps left the instruction manual password in there. Here's the commands I had to issue;

keystone user-list # to get the id

keystone user-delete cbadb6fff68a4165a09ba9db75cc850d

keystone user-create --name=glance --pass=password --email=me@gmail.com

keystone user-role-add --user=glance --tenant=service --role=admin

2014-06-04 22:48:18 -0500 commented answer glance image-create returns invalid credentials

I had this problem and it turned out I had not changed my password to the correct value in the glance-registry.conf for the line: connection = mysql://glance:password@controller/glance

2014-06-04 21:43:40 -0500 commented answer glance-manage db_sync problem

I had this error and it was caused because I left the password for glance as it was in the instructions when I pasted it into the glance-api.conf. When i replaced it with my chosen password it worked.

2014-06-04 21:41:44 -0500 received badge  Supporter (source)
2014-05-18 12:07:11 -0500 commented question Icehouse initial setup, error creating admin in keystone

For me the problem was a few steps back in the installation procedure - Keystone database configuraiton file setup.

for me the fix was to change the line in /etc/keystone/keystone.com from: connection = mysql://keystone:mypass@controller/keystone to: connection = mysql://keystone:mypass@locahost/keystone

I've tried to debug why the name controller is not usefull in my machine, it can be pinged. It is not the HOSTNAME - but when I tried to change my Linux HOSTNAME to controller this didn't seem to fix it and just substituting localhost did. As I understand it this database and keystone instance will only be acessed form this 1 node so this is OK for me.

I was then able to go onto step 5 and create the Keystone database successfully (which is a point I must have either skipped or failed before).