[Openstack] error creating instance
Andreas Scheuring
scheuran at linux.vnet.ibm.com
Tue Jun 30 06:43:17 UTC 2015
Now all makes absolutely sense:
+---------------------------+--------------------------------------+
| Field | Value |
+---------------------------+--------------------------------------+
| admin_state_up | True |
| id | 7a344656-815c-4116-b697-b52f9fdc6e4c |
| name | demo-net |
| provider:network_type | vlan |
| provider:physical_network | external |
| provider:segmentation_id | 1102 |
| router:external | False |
| shared | False |
| status | ACTIVE |
| subnets | c57880bf-2869-4b1d-b31c-0d2d083d05e4 |
| tenant_id | f976b7c713c64b028c0e89f3956795ed |
+---------------------------+--------------------------------------+
This is you demo network. It's mapped to the pyhsical network
"external" (defined in bridgemapping) and uses vlan.
But that the wrong way. If I get you right, you still want to use gre
but now over your static vlan, right? So what you need to do is, to
delete your demo-net.
> neutron net-delete 7a344656-815c-4116-b697-b52f9fdc6e4c
And just create a new one without specifying any provider attributes
> neutron net-create ...
Not sure, but I guess it's sufficient to specify a name!
> neutron net-show <your-new-net>
It should look somehting like this:
--> no pyhsical network
--> network_type = gre
+---------------------------+--------------------------------------+
> | Field | Value |
> +---------------------------+--------------------------------------+
> | admin_state_up | True |
> | id | ef6552a5-be39-4bcc-9dde-2a200eaca64d |
> | mtu | 0 |
> | name | private |
> | provider:network_type | vxlan |
> | provider:physical_network | |
> | provider:segmentation_id | 1001 |
> | router:external | False |
> | shared | False |
> | status | ACTIVE |
> | subnets | 4b539feb-b104-4f69-83ba-76f746a2c592 |
> | | ac255618-afe9-4aea-b86d-b662b68e9d9d |
> | tenant_id | 3c4ddcff52a74f2b97b71392300aa74d |
> +---------------------------+--------------------------------------+
If you want to switch over totally to vlan (not using gre in your static
vlan anymore), you have to reconfigure the ml2 config files. But I'm not
sure, if dynamic Openstack vlans nested into a static host vlan work
out. But let's discuss this if relevant.
You can also ping me on irc (freenode, #openstack, to speed up
debugging. My nic name is 'scheuran'.
Andreas
On Mo, 2015-06-29 at 15:54 +0000, Yngvi Páll Þorfinnsson wrote:
> OK,
>
> This is the network list
>
> root at controller2:/# neutron net-list
> +--------------------------------------+-------------+-----------------------------------------------------+
> | id | name | subnets |
> +--------------------------------------+-------------+-----------------------------------------------------+
> | 1cb21927-6996-4022-8d3e-292390dad6d0 | ext_net1101 | 7b84ec73-eaa7-479f-872f-41c6cb2083c5 157.157.8.0/24 |
> | 7a344656-815c-4116-b697-b52f9fdc6e4c | demo-net | c57880bf-2869-4b1d-b31c-0d2d083d05e4 172.22.18.0/24 |
> +--------------------------------------+-------------+-----------------------------------------------------+
> root at controller2:/#
> root at controller2:/#
> root at controller2:/# neutron net-show 1cb21927-6996-4022-8d3e-292390dad6d0
> +---------------------------+--------------------------------------+
> | Field | Value |
> +---------------------------+--------------------------------------+
> | admin_state_up | True |
> | id | 1cb21927-6996-4022-8d3e-292390dad6d0 |
> | name | ext_net1101 |
> | provider:network_type | vlan |
> | provider:physical_network | external |
> | provider:segmentation_id | 1101 |
> | router:external | True |
> | shared | False |
> | status | ACTIVE |
> | subnets | 7b84ec73-eaa7-479f-872f-41c6cb2083c5 |
> | tenant_id | c96aec0da5e542ad8e3198aaccc498c7 |
> +---------------------------+--------------------------------------+
> root at controller2:/# neutron net-show 7a344656-815c-4116-b697-b52f9fdc6e4c
> +---------------------------+--------------------------------------+
> | Field | Value |
> +---------------------------+--------------------------------------+
> | admin_state_up | True |
> | id | 7a344656-815c-4116-b697-b52f9fdc6e4c |
> | name | demo-net |
> | provider:network_type | vlan |
> | provider:physical_network | external |
> | provider:segmentation_id | 1102 |
> | router:external | False |
> | shared | False |
> | status | ACTIVE |
> | subnets | c57880bf-2869-4b1d-b31c-0d2d083d05e4 |
> | tenant_id | f976b7c713c64b028c0e89f3956795ed |
> +---------------------------+--------------------------------------+
> root at controller2:/#
>
> and this is how I created the external network, with CMD ;
>
> neutron net-create ext_net1101 --provider:network_type vlan --provider:physical_network external --provider:segmentation_id 1101 --router:external=True
>
>
> But there seems not to be info on this one
> root at controller2:/# neutron net-show cf6489c4-7ed6-43dc-85aa-f4b8c6b501ca
> Unable to find network with name 'cf6489c4-7ed6-43dc-85aa-f4b8c6b501ca'
>
>
> best regards
> Yngvi
>
>
> -----Original Message-----
> From: Andreas Scheuring [mailto:scheuran at linux.vnet.ibm.com]
> Sent: 29. júní 2015 15:25
> To: Yngvi Páll Þorfinnsson
> Cc: uwe.sauter.de at gmail.com; openstack at lists.openstack.org
> Subject: Re: [Openstack] error creating instance
>
>
>
> Attempting to bind port 2bf4a49b-2ad6-4ead-a656-65814ad0724e on network 7a344656-815c-4116-b697-b52f9fdc6e4c
> bind_port /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py:57
> 2015-06-29 14:28:55.924 5328 DEBUG
> neutron.plugins.ml2.drivers.mech_agent
> [req-9fe66e60-1a70-4ad6-b21e-ef91aca8a931 None] Checking agent:
> {'binary': u'neutron-openvswitch-agent', 'description': None,
> 'admin_state_up': True, 'heartbeat_timestamp': datetime.datetime(2015, 6, 29, 14, 28, 45), 'alive': True, 'id':
> u'1c06fb08-105c-4659-ae0e-4a905931311e', 'topic': u'N/A', 'host':
> u'compute5', 'agent_type': u'Open vSwitch agent', 'started_at':
> datetime.datetime(2015, 6, 29, 14, 27, 45), 'created_at':
> datetime.datetime(2015, 6, 26, 14, 51, 14), 'configurations':
> {u'arp_responder_enabled': False, u'tunneling_ip': u'172.22.15.17',
> u'devices': 0, u'l2_population': False, u'tunnel_types': [u'gre'],
> u'enable_distributed_routing': False, u'bridge_mappings': {}}} bind_port /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_agent.py:65
> 2015-06-29 14:28:55.925 5328 DEBUG
> neutron.plugins.ml2.drivers.mech_openvswitch
> [req-9fe66e60-1a70-4ad6-b21e-ef91aca8a931 None] Checking segment:
> {'segmentation_id': 1102L, 'physical_network': u'external', 'id':
> u'cf6489c4-7ed6-43dc-85aa-f4b8c6b501ca', 'network_type': u'vlan'} for
> mappings: {} with tunnel_types: [u'gre'] check_segment_for_agent /usr/lib/python2.7/dist-packages/neutron/plugins/ml2/drivers/mech_openvswitch.py:52
>
>
>
> ===
> Checking segment: {'segmentation_id': 1102L, 'physical_network':u'external', 'id':
> u'cf6489c4-7ed6-43dc-85aa-f4b8c6b501ca', 'network_type': u'vlan'} for mappings: {} with tunnel_types: [u'gre']
>
> This looks strange: Seems like your tenant network has a physical_network of type vlan assigned. That shouldn't be the case.
>
> Could you please provide the following information:
>
> Information of all Openstack networks available:
>
> > neutron net-list
>
> > neutron net-show <uuid>
>
> Especially of this one:
> > neturon net-show cf6489c4-7ed6-43dc-85aa-f4b8c6b501ca
>
>
> Usually your network should look like this (in this case vxlan):
>
> +---------------------------+--------------------------------------+
> | Field | Value |
> +---------------------------+--------------------------------------+
> | admin_state_up | True |
> | id | ef6552a5-be39-4bcc-9dde-2a200eaca64d |
> | mtu | 0 |
> | name | private |
> | provider:network_type | vxlan |
> | provider:physical_network | |
> | provider:segmentation_id | 1001 |
> | router:external | False |
> | shared | False |
> | status | ACTIVE |
> | subnets | 4b539feb-b104-4f69-83ba-76f746a2c592 |
> | | ac255618-afe9-4aea-b86d-b662b68e9d9d |
> | tenant_id | 3c4ddcff52a74f2b97b71392300aa74d |
> +---------------------------+--------------------------------------+
>
> How did you create yours? via the UI? Or are you attaching your instance to the external network instead? In any case you need to attach it to your tenant network!! If it's not visible via the UI, maybe you have to switch to another tenant to get it.
>
> Hope we're close to finding the issue ;)
>
>
> Andreas
>
>
More information about the Openstack
mailing list