Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

No available ports for floating IPs in new project

So, I've gotten this working within the initial admin project. I can churn out instances, assign floating IPs and access them on my network. Trying to keep this as simple as possible, I've two networks: public = 10.5.0.0/16 private=10.50.0.0/16

In my floating IP allocation, I've set 10.5.2.1 to 10.5.254.254. Like I said, simple, it's all one company, not need for complexity. So I make both of these networks shared, and they can be seen from both projects. When I launch an new instance in the other project (we'll call it newproj), I get a properly assigned address from the allocation pool and the instance starts fine. But when I go to associate an IP, there are "no ports available". Running neutron port-list shows that the port IS being created. In the dashboard, I can see the ports listed under that network listed as UP.

I tried the neutron.py patch suggested in this thread with no luck: https://ask.openstack.org/en/question/51634/juno-dvr-associate-floating-ip-reported-no-ports-available/

I also looked at this thread: https://ask.openstack.org/en/question/53507/juno-could-not-associate-floating-ip-no-ports-available/ which suggested recreating the private net in that project. Which begs the question, do I have to have a separate private network for each project? Can I not use a shared private net amongst ALL projects?

I see no errors in any of the logs, so I'm not really even sure what you might need to see to help resolve this.

No available ports for floating IPs in new project

So, I've gotten this working within the initial admin project. I can churn out instances, assign floating IPs and access them on my network. Trying to keep this as simple as possible, I've two networks: public = 10.5.0.0/16 private=10.50.0.0/16

In my floating IP allocation, I've set 10.5.2.1 to 10.5.254.254. Like I said, simple, it's all one company, not need for complexity. So I make both of these networks shared, and they can be seen from both projects. When I launch an new instance in the other project (we'll call it newproj), I get a properly assigned address from the allocation pool and the instance starts fine. But when I go to associate an IP, there are "no ports available". Running neutron port-list shows that the port IS being created. In the dashboard, I can see the ports listed under that network listed as UP.

I tried the neutron.py patch suggested in this thread with no luck: https://ask.openstack.org/en/question/51634/juno-dvr-associate-floating-ip-reported-no-ports-available/

I also looked at this thread: https://ask.openstack.org/en/question/53507/juno-could-not-associate-floating-ip-no-ports-available/ which suggested recreating the private net in that project. Which begs the question, do I have to have a separate private network for each project? Can I not use a shared private net amongst ALL projects?

I see no errors in any of the logs, so I'm not really even sure what you might need to see to help resolve this.

UPDATE 1

Ran this in new project "tp" source ~/keystonerc_tp neutron router-create tp-router neutron net-create tp-private neutron subnet-create --name tp-private_subnet tp-private 10.50.4.0/22 --allocation-pool start=10.50.4.11,end=10.50.7.254 neutron router-interface-add tp-router tp-private_subnet

[root@os-node-1 ~(keystone_tp)]# neutron router-list
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| id                                   | name      | external_gateway_info                                                                                                                                                                  | distributed | ha    |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| 7f023ced-9320-4e08-9fe9-35bf924ab47b | router1   | {"network_id": "92dc875c-f6c1-4ac5-bd62-65f1fd0536db", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "fcbb1684-1c67-472a-85b3-30a31fa7de4a", "ip_address": "10.5.0.200"}]} | False       | False |
| e2e331a9-8c2a-4988-8353-b62c929777ff | tp-router | null                                                                                                                                                                                   | False       | False |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

[root@os-node-1 ~(keystone_tp)]# neutron net-list
+--------------------------------------+------------+---------------------------------------------------+
| id                                   | name       | subnets                                           |
+--------------------------------------+------------+---------------------------------------------------+
| 61598905-8013-4414-923f-2090d5e748bf | tp-private | dce4ed19-22b2-4a37-86ea-9da55708b94a 10.50.4.0/22 |
| 92dc875c-f6c1-4ac5-bd62-65f1fd0536db | public     | fcbb1684-1c67-472a-85b3-30a31fa7de4a 10.5.0.0/16  |
| 469751f2-8a62-413d-b966-8a5bb9812338 | private    | c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 10.50.0.0/22 |
+--------------------------------------+------------+---------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron subnet-list
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| id                                   | name              | cidr         | allocation_pools                               |
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| dce4ed19-22b2-4a37-86ea-9da55708b94a | tp-private_subnet | 10.50.4.0/22 | {"start": "10.50.4.11", "end": "10.50.7.254"}  |
| fcbb1684-1c67-472a-85b3-30a31fa7de4a | public_subnet     | 10.5.0.0/16  | {"start": "10.5.0.200", "end": "10.5.0.254"}   |
| c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 | private_subnet    | 10.50.0.0/22 | {"start": "10.50.0.100", "end": "10.50.3.254"} |
+--------------------------------------+-------------------+--------------+------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron router-port-list tp-router
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                        |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| c2a3dbae-f590-460a-bdbb-acc182f7b071 |      | fa:16:3e:bd:2f:64 | {"subnet_id": "dce4ed19-22b2-4a37-86ea-9da55708b94a", "ip_address": "10.50.4.1"} |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# nova list
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| ID                                   | Name        | Status | Task State | Power State | Networks              |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| c20f973a-a352-41aa-88db-dc0facfdfbbf | tp-cirros-5 | ACTIVE | -          | Running     | tp-private=10.50.4.11 |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id                                   | fixed_ip_address | floating_ip_address | port_id                              |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 508cb197-b8b5-4bef-8238-28cc2242bb7e |                  | 10.5.0.202          |                                      |
| 63ff1407-580c-4c60-b01b-eede2c964fdb |                  | 10.5.0.203          |                                      |
| e869df32-b14e-40e1-aaac-9c059c88e7d8 | 10.50.0.100      | 10.5.0.201          | a1fc8427-dbc8-478b-9238-c63454293b18 |
+--------------------------------------+------------------+---------------------+--------------------------------------+

The net ID I used here I got from the dashboard entry for that port. I couldn't find a way to list it on CLI

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-associate 508cb197-b8b5-4bef-8238-28cc2242bb7e c87963a2-eafa-4979-97aa-3df33ab06834
Not Found (HTTP 404) (Request-ID: req-caf06073-f6ec-4e6e-8c23-5009ee50cccf)

No available ports for floating IPs in new project

So, I've gotten this working within the initial admin project. I can churn out instances, assign floating IPs and access them on my network. Trying to keep this as simple as possible, I've two networks: public = 10.5.0.0/16 private=10.50.0.0/16

In my floating IP allocation, I've set 10.5.2.1 to 10.5.254.254. Like I said, simple, it's all one company, not need for complexity. So I make both of these networks shared, and they can be seen from both projects. When I launch an new instance in the other project (we'll call it newproj), I get a properly assigned address from the allocation pool and the instance starts fine. But when I go to associate an IP, there are "no ports available". Running neutron port-list shows that the port IS being created. In the dashboard, I can see the ports listed under that network listed as UP.

I tried the neutron.py patch suggested in this thread with no luck: https://ask.openstack.org/en/question/51634/juno-dvr-associate-floating-ip-reported-no-ports-available/

I also looked at this thread: https://ask.openstack.org/en/question/53507/juno-could-not-associate-floating-ip-no-ports-available/ which suggested recreating the private net in that project. Which begs the question, do I have to have a separate private network for each project? Can I not use a shared private net amongst ALL projects?

I see no errors in any of the logs, so I'm not really even sure what you might need to see to help resolve this.

UPDATE 1

Ran this in new project "tp" source ~/keystonerc_tp neutron router-create tp-router neutron net-create tp-private neutron subnet-create --name tp-private_subnet tp-private 10.50.4.0/22 --allocation-pool start=10.50.4.11,end=10.50.7.254 neutron router-interface-add tp-router tp-private_subnet

[root@os-node-1 ~(keystone_tp)]# neutron router-list
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| id                                   | name      | external_gateway_info                                                                                                                                                                  | distributed | ha    |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| 7f023ced-9320-4e08-9fe9-35bf924ab47b | router1   | {"network_id": "92dc875c-f6c1-4ac5-bd62-65f1fd0536db", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "fcbb1684-1c67-472a-85b3-30a31fa7de4a", "ip_address": "10.5.0.200"}]} | False       | False |
| e2e331a9-8c2a-4988-8353-b62c929777ff | tp-router | null                                                                                                                                                                                   | False       | False |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

[root@os-node-1 ~(keystone_tp)]# neutron net-list
+--------------------------------------+------------+---------------------------------------------------+
| id                                   | name       | subnets                                           |
+--------------------------------------+------------+---------------------------------------------------+
| 61598905-8013-4414-923f-2090d5e748bf | tp-private | dce4ed19-22b2-4a37-86ea-9da55708b94a 10.50.4.0/22 |
| 92dc875c-f6c1-4ac5-bd62-65f1fd0536db | public     | fcbb1684-1c67-472a-85b3-30a31fa7de4a 10.5.0.0/16  |
| 469751f2-8a62-413d-b966-8a5bb9812338 | private    | c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 10.50.0.0/22 |
+--------------------------------------+------------+---------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron subnet-list
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| id                                   | name              | cidr         | allocation_pools                               |
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| dce4ed19-22b2-4a37-86ea-9da55708b94a | tp-private_subnet | 10.50.4.0/22 | {"start": "10.50.4.11", "end": "10.50.7.254"}  |
| fcbb1684-1c67-472a-85b3-30a31fa7de4a | public_subnet     | 10.5.0.0/16  | {"start": "10.5.0.200", "end": "10.5.0.254"}   |
| c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 | private_subnet    | 10.50.0.0/22 | {"start": "10.50.0.100", "end": "10.50.3.254"} |
+--------------------------------------+-------------------+--------------+------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron router-port-list tp-router
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                        |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| c2a3dbae-f590-460a-bdbb-acc182f7b071 |      | fa:16:3e:bd:2f:64 | {"subnet_id": "dce4ed19-22b2-4a37-86ea-9da55708b94a", "ip_address": "10.50.4.1"} |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# nova list
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| ID                                   | Name        | Status | Task State | Power State | Networks              |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| c20f973a-a352-41aa-88db-dc0facfdfbbf | tp-cirros-5 | ACTIVE | -          | Running     | tp-private=10.50.4.11 |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id                                   | fixed_ip_address | floating_ip_address | port_id                              |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 508cb197-b8b5-4bef-8238-28cc2242bb7e |                  | 10.5.0.202          |                                      |
| 63ff1407-580c-4c60-b01b-eede2c964fdb |                  | 10.5.0.203          |                                      |
| e869df32-b14e-40e1-aaac-9c059c88e7d8 | 10.50.0.100      | 10.5.0.201          | a1fc8427-dbc8-478b-9238-c63454293b18 |
+--------------------------------------+------------------+---------------------+--------------------------------------+

[root@os-node-1 neutron(keystone_tp)]# neutron port-list --device-id c20f973a-a352-41aa-88db-dc0facfdfbbf
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                         |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
| c87963a2-eafa-4979-97aa-3df33ab06834 |      | fa:16:3e:01:07:1b | {"subnet_id": "dce4ed19-22b2-4a37-86ea-9da55708b94a", "ip_address": "10.50.4.11"} |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+

The net ID I used here I got from the dashboard entry for that port. I couldn't find a way to list it on CLI

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-associate 508cb197-b8b5-4bef-8238-28cc2242bb7e c87963a2-eafa-4979-97aa-3df33ab06834
Not Found (HTTP 404) (Request-ID: req-caf06073-f6ec-4e6e-8c23-5009ee50cccf)

No available ports for floating IPs in new project

So, I've gotten this working within the initial admin project. I can churn out instances, assign floating IPs and access them on my network. Trying to keep this as simple as possible, I've two networks: public = 10.5.0.0/16 private=10.50.0.0/16

In my floating IP allocation, I've set 10.5.2.1 to 10.5.254.254. Like I said, simple, it's all one company, not need for complexity. So I make both of these networks shared, and they can be seen from both projects. When I launch an new instance in the other project (we'll call it newproj), I get a properly assigned address from the allocation pool and the instance starts fine. But when I go to associate an IP, there are "no ports available". Running neutron port-list shows that the port IS being created. In the dashboard, I can see the ports listed under that network listed as UP.

I tried the neutron.py patch suggested in this thread with no luck: https://ask.openstack.org/en/question/51634/juno-dvr-associate-floating-ip-reported-no-ports-available/

I also looked at this thread: https://ask.openstack.org/en/question/53507/juno-could-not-associate-floating-ip-no-ports-available/ which suggested recreating the private net in that project. Which begs the question, do I have to have a separate private network for each project? Can I not use a shared private net amongst ALL projects?

I see no errors in any of the logs, so I'm not really even sure what you might need to see to help resolve this.

UPDATE 1

Ran this in new project "tp" source ~/keystonerc_tp neutron router-create tp-router neutron net-create tp-private neutron subnet-create --name tp-private_subnet tp-private 10.50.4.0/22 --allocation-pool start=10.50.4.11,end=10.50.7.254 neutron router-interface-add tp-router tp-private_subnet

[root@os-node-1 ~(keystone_tp)]# neutron router-list
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| id                                   | name      | external_gateway_info                                                                                                                                                                  | distributed | ha    |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+
| 7f023ced-9320-4e08-9fe9-35bf924ab47b | router1   | {"network_id": "92dc875c-f6c1-4ac5-bd62-65f1fd0536db", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "fcbb1684-1c67-472a-85b3-30a31fa7de4a", "ip_address": "10.5.0.200"}]} | False       | False |
| e2e331a9-8c2a-4988-8353-b62c929777ff | tp-router | null                                                                                                                                                                                   | False       | False |
+--------------------------------------+-----------+----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+-------------+-------+

[root@os-node-1 ~(keystone_tp)]# neutron net-list
+--------------------------------------+------------+---------------------------------------------------+
| id                                   | name       | subnets                                           |
+--------------------------------------+------------+---------------------------------------------------+
| 61598905-8013-4414-923f-2090d5e748bf | tp-private | dce4ed19-22b2-4a37-86ea-9da55708b94a 10.50.4.0/22 |
| 92dc875c-f6c1-4ac5-bd62-65f1fd0536db | public     | fcbb1684-1c67-472a-85b3-30a31fa7de4a 10.5.0.0/16  |
| 469751f2-8a62-413d-b966-8a5bb9812338 | private    | c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 10.50.0.0/22 |
+--------------------------------------+------------+---------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron subnet-list
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| id                                   | name              | cidr         | allocation_pools                               |
+--------------------------------------+-------------------+--------------+------------------------------------------------+
| dce4ed19-22b2-4a37-86ea-9da55708b94a | tp-private_subnet | 10.50.4.0/22 | {"start": "10.50.4.11", "end": "10.50.7.254"}  |
| fcbb1684-1c67-472a-85b3-30a31fa7de4a | public_subnet     | 10.5.0.0/16  | {"start": "10.5.0.200", "end": "10.5.0.254"}   |
| c52bb9ca-1335-4f8b-8da7-6ba4254b70c9 | private_subnet    | 10.50.0.0/22 | {"start": "10.50.0.100", "end": "10.50.3.254"} |
+--------------------------------------+-------------------+--------------+------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# neutron router-port-list tp-router
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                        |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+
| c2a3dbae-f590-460a-bdbb-acc182f7b071 |      | fa:16:3e:bd:2f:64 | {"subnet_id": "dce4ed19-22b2-4a37-86ea-9da55708b94a", "ip_address": "10.50.4.1"} |
+--------------------------------------+------+-------------------+----------------------------------------------------------------------------------+

[root@os-node-1 ~(keystone_tp)]# nova list
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| ID                                   | Name        | Status | Task State | Power State | Networks              |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+
| c20f973a-a352-41aa-88db-dc0facfdfbbf | tp-cirros-5 | ACTIVE | -          | Running     | tp-private=10.50.4.11 |
+--------------------------------------+-------------+--------+------------+-------------+-----------------------+

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-list
+--------------------------------------+------------------+---------------------+--------------------------------------+
| id                                   | fixed_ip_address | floating_ip_address | port_id                              |
+--------------------------------------+------------------+---------------------+--------------------------------------+
| 508cb197-b8b5-4bef-8238-28cc2242bb7e |                  | 10.5.0.202          |                                      |
| 63ff1407-580c-4c60-b01b-eede2c964fdb |                  | 10.5.0.203          |                                      |
| e869df32-b14e-40e1-aaac-9c059c88e7d8 | 10.50.0.100      | 10.5.0.201          | a1fc8427-dbc8-478b-9238-c63454293b18 |
+--------------------------------------+------------------+---------------------+--------------------------------------+

[root@os-node-1 neutron(keystone_tp)]# neutron port-list --device-id c20f973a-a352-41aa-88db-dc0facfdfbbf
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
| id                                   | name | mac_address       | fixed_ips                                                                         |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+
| c87963a2-eafa-4979-97aa-3df33ab06834 |      | fa:16:3e:01:07:1b | {"subnet_id": "dce4ed19-22b2-4a37-86ea-9da55708b94a", "ip_address": "10.50.4.11"} |
+--------------------------------------+------+-------------------+-----------------------------------------------------------------------------------+

The net ID I used here I got from the dashboard entry for that port. I couldn't find a way to list it on CLI

[root@os-node-1 neutron(keystone_tp)]# neutron floatingip-associate 508cb197-b8b5-4bef-8238-28cc2242bb7e c87963a2-eafa-4979-97aa-3df33ab06834
Not Found (HTTP 404) (Request-ID: req-caf06073-f6ec-4e6e-8c23-5009ee50cccf)

UPDATE 2 [root@os-node-1 ~(keystone_tp)]# neutron -v floatingip-associate 508cb197-b8b5-4bef-8238-28cc2242bb7e c87963a2-eafa-4979-97aa-3df33ab06834 DEBUG: keystoneclient.session REQ: curl -i -X GET http://10.5.0.11:5000/v2.0/ -H "Accept: application/json" -H "User-Agent: python-keystoneclient" DEBUG: keystoneclient.session RESP: [200] {'date': 'Mon, 08 Dec 2014 17:57:00 GMT', 'content-type': 'application/json', 'content-length': '419', 'vary': 'X-Auth-Token'} RESP BODY: {"version": {"status": "stable", "updated": "2014-04-17T00:00:00Z", "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v2.0+json"}, {"base": "application/xml", "type": "application/vnd.openstack.identity-v2.0+xml"}], "id": "v2.0", "links": [{"href": "http://10.5.0.11:5000/v2.0/", "rel": "self"}, {"href": "http://docs.openstack.org/", "type": "text/html", "rel": "describedby"}]}}

DEBUG: neutronclient.neutron.v2_0.floatingip.AssociateFloatingIP run(Namespace(fixed_ip_address=None, floatingip_id=u'508cb197-b8b5-4bef-8238-28cc2242bb7e', port_id=u'c87963a2-eafa-4979-97aa-3df33ab06834', request_format='json')) DEBUG: keystoneclient.auth.identity.v2 Making authentication request to http://10.5.0.11:5000/v2.0/tokens DEBUG: keystoneclient.session REQ: curl -i -X PUT http://10.5.0.11:9696/v2.0/floatingips/508cb197-b8b5-4bef-8238-28cc2242bb7e.json -H "User-Agent: python-neutronclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: TOKEN_REDACTED" -d '{"floatingip": {"port_id": "c87963a2-eafa-4979-97aa-3df33ab06834"}}' DEBUG: keystoneclient.session RESP: DEBUG: keystoneclient.session Request returned failure status: 404 ERROR: neutronclient.shell Not Found (HTTP 404) (Request-ID: req-b1c86c7e-e82b-471b-b773-fe2d20e5acfb) Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/neutronclient/shell.py", line 691, in run_subcommand return run_command(cmd, cmd_parser, sub_argv) File "/usr/lib/python2.7/site-packages/neutronclient/shell.py", line 90, in run_command return cmd.run(known_args) File "/usr/lib/python2.7/site-packages/neutronclient/neutron/v2_0/floatingip.py", line 120, in run {'floatingip': update_dict}) File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 98, in with_params ret = self.function(instance, args, *kwargs) File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 458, in update_floatingip return self.put(self.floatingip_path % (floatingip), body=body) File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 1329, in put headers=headers, params=params) File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 1297, in retry_request headers=headers, params=params) File "/usr/lib/python2.7/site-packages/neutronclient/v2_0/client.py", line 1240, in do_request content_type=self.content_type()) File "/usr/lib/python2.7/site-packages/neutronclient/client.py", line 319, in do_request return self.request(url, method, *kwargs) File "/usr/lib/python2.7/site-packages/neutronclient/client.py", line 63, in request return self._request(url, method, body=body, headers=headers, *kwargs) File "/usr/lib/python2.7/site-packages/neutronclient/client.py", line 314, in _request *kwargs) File "/usr/lib/python2.7/site-packages/keystoneclient/utils.py", line 318, in inner return func(args, **kwargs) File "/usr/lib/python2.7/site-packages/keystoneclient/session.py", line 346, in request raise exceptions.from_response(resp, method, url) NotFound: Not Found (HTTP 404) (Request-ID: req-b1c86c7e-e82b-471b-b773-fe2d20e5acfb) Not Found (HTTP 404) (Request-ID: req-b1c86c7e-e82b-471b-b773-fe2d20e5acfb)