Ask Your Question
0

cannot add the default external network to an instance

asked 2016-12-09 17:02:21 -0500

jamesopst gravatar image

updated 2016-12-14 11:01:39 -0500

hi,

I cannot add the default external network to an instance, either via Horizon or via the Nova command line. In Horizon I cannot add the external to an existing instance and I if I add it while creating (Launch) an instance the instance will fail to create.

any help or suggestions I would greatly appreciate. I've create a new external network and that shows the same issue.

here are the latest logs:

http://www.jokken.com/downloads/ctlr-neutron-all.log (ctrlr neutron)

http://www.jokken.com/downloads/ctlr-nova.log (ctrlr nova)

http://www.jokken.com/downloads/comp-neutron-all.log (compute neutron)

http://www.jokken.com/downloads/comp-nova.log (compute nova)

some interesting parts of the Controller and Compute node's Nova logs

<179>Dec 12 17:58:12 node-1 nova-api: 2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions [req-6837530a-bf7f-4606-96d5-a810a0417802 19d9fea8ad7744779ba2c81e1ad36e76 fcff98f1c7a34a86be56c0a3d069c280 - - -] Unexpected exception in API method
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions Traceback (most recent call last):
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/api/openstack/extensions.py", line 478, in wrapped
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     return f(*args, **kwargs)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/api/validation/__init__.py", line 73, in wrapper
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     return func(*args, **kwargs)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/api/openstack/compute/attach_interfaces.py", line 117, in create
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     instance, network_id, port_id, req_ip)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 234, in wrapped
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     return func(self, context, target, *args, **kwargs)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 223, in inner
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     return function(self, context, instance, *args, **kwargs)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 204, in inner
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     return f(self, context, instance, *args, **kw)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/compute/api.py", line 3177, in attach_interface
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     requested_ip=requested_ip)
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions   File "/usr/lib/python2.7/dist-packages/nova/compute/rpcapi.py", line 365, in attach_interface
2016-12-12 17:58:12.364 8853 ERROR nova.api.openstack.extensions     port_id=port_id, requested_ip=requested_ip)
2016-12-12 17:58:12 ...
(more)
edit retag flag offensive close merge delete

Comments

Most likely a misconfiguration. Debug logging will give you more information. Also, your network topology is unclear - do you have a tenant network connected to external with a Neutron router or do you connect the instance directly to the external network (only the admin can do the latter afaik)?

Bernd Bausch gravatar imageBernd Bausch ( 2016-12-09 19:09:01 -0500 )edit

thanks for the reply

I am using the admin account and believe I am connecting the instance directly to the external network. i've reproduced with debug and changed the original question to contain the debug logs

jamesopst gravatar imagejamesopst ( 2016-12-10 09:09:39 -0500 )edit

Perhaps the neutron server log on the controller node contains a clue.

Bernd Bausch gravatar imageBernd Bausch ( 2016-12-11 01:59:11 -0500 )edit

ok, I have reproduced the issue and edited the original question with the neutron and nova logs. The issue is around 17:58:12 give or take

I believe the port is: bf22bf18-a5e2-4d55-9523-b1126ad48ea9

i see: Exception during message handling: Binding failed for port (with a traceback)

thanks again

jamesopst gravatar imagejamesopst ( 2016-12-12 18:15:50 -0500 )edit

Bernd were you able to have a look at those logs in the links I put in the original question? I put some of the snippets i thought might be important in the original question too.

jamesopst gravatar imagejamesopst ( 2016-12-14 10:47:53 -0500 )edit

2 answers

Sort by » oldest newest most voted
0

answered 2017-07-20 15:54:12 -0500

jamesopst gravatar image

i had an expert in our company help with this. he shared this with me. it might help others, it got me what I wanted: add the external network to an instance. So I don't even use the internal_net network on instances anymore. and even though the external network is called the floating_net I don't think the term "floating" really is correct anymore.

expert said this: ….I’ve managed to get VM instances directly on the floating network (of course that makes that name rubbish now!), I’ve made the changes on one of the compute nodes (node-15) and tested it there. I'll leave you the exercise of changing the rest of the compute nodes! here are the steps:

1.  Changed tst_cloud_floating_net__subnet to support DHCP
2.  Changed enable_metadata_network = True in /etc/neutron/dhcp_agent.ini on all 3 controller nodes  (node-1, node-2, node-3)
3.  service neutron-dhcp-agent restart on all 3 controller nodes
4.  Added physnet2 mapping to /etc/neutron/plugins/ml2/ml2_conf.ini on node-15 (This needs doing for all other compute nodes)
a.  bridge_mappings=physnet2:br-prv,physnet1:br-floating
5.  service neutron-plugin-openvswitch-agent restart on node-15 (needs doing on all compute nodes after the above edit)
edit flag offensive delete link more
0

answered 2017-04-01 17:13:17 -0500

AndriusF47 gravatar image

You cannot add external network directly to instance. Use neutron routers to link private network to external networks and assign floating ip.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

Stats

Asked: 2016-12-09 17:02:21 -0500

Seen: 194 times

Last updated: Jul 20 '17