New Question
0

Getting the following error over and over. No adapter after the first will configure [closed]

asked 2014-07-30 06:02:24 +0200

fortinj66 gravatar image

updated 2014-08-04 13:40:21 +0200

Using Havana plugin and VLAN setup

http://paste.openstack.org/show/89959/

(admin edit: i've moved the error dump to http://paste.openstack.org)

edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by Claudiu Belu
close date 2016-11-09 19:37:21.270351

Comments

Update: I updated OpenStack to Icehouse and used the Icehouse HyperV installer and still have the same issue. No adapter after the first will configure, even on new VMs. If I remove all the VMs and then recreate them I still get onlly one adapter configured. Very puzzling...

fortinj66 gravatar imagefortinj66 ( 2014-07-30 23:16:44 +0200 )edit

There may be something wrong with neutron config, ml2 config? Paste it and let's see.

chris gravatar imagechris ( 2014-08-21 21:36:56 +0200 )edit

It looks like something wrong with the OpenStack deployment, especially the Neutron controller, as the RPC calls to it fail (as if those methods don't exist on the Neutron Controller).

Claudiu Belu gravatar imageClaudiu Belu ( 2016-11-09 19:38:50 +0200 )edit

2 answers

Sort by » oldest newest most voted
2

answered 2014-08-22 21:04:40 +0200

itoader gravatar image

We set up the environment consisting in: - linux SLES 11 with http://docs.openstack.org/icehouse/in... - 1 hyperv node Windows Server 2012 R2 with the 2014.1 Icehouse release

We issued the following nova command to boot a vm:

nova boot --image cfa95750-e6d5-4af5-94e0-838a42ea8f33 --flavor m1.tiny --key_name demo-key --security-groups default --nic net-id=c5598cd4-1c12-4baf-a60e-db0bd63ee040  --nic net-id=c5598cd4-1c12-4baf-a60e-db0bd63ee04 vm

Neutron has been configured using the ml2 plugin.

On hyperv everything is ok here is the vlan configuration:

PS C:\Users\Administrator> Get-VMNetworkAdapterVlan instance-00000067

VMName VMNetworkAdapterName Mode VlanList ------ -------------------- ---- -------- instance-00000067 256d2bb3-85cb-41fa-ac3e-d7c837090528 Access 504 instance-00000067 619b258b-3b68-427f-b121-949d30004f7e Access 505

Could you please share your configuration to see what are the differences?

edit flag offensive delete link more
0

answered 2014-08-04 14:43:37 +0200

alexpilotti gravatar image

As by email follow up, we cannot reproduce this issue on Ubuntu or RDO Icehouse with Hyper-V 2012 R2 nodes. We're currently setting up a matching SLES environment and we'll get back as soon as we have some results.

Thanks

edit flag offensive delete link more

Question Tools

2 followers

Stats

Asked: 2014-07-30 06:02:24 +0200

Seen: 331 times

Last updated: Aug 22 '14