Revision history [back]

Networking Problems integrating Newton & VMWare vCenter

I have Newton setup with Neutron and linux-bridges, where one of the compute nodes is configured to use VMwareVCDriver, however, when instantiating a VM and preparing the networking part, nova-compute complains about "vif type bridge not supported"

My nova.conf relevant config is, besides the driver and authentication credentials:

[vmware]
 ...
cluster_name = Cluster01
integration_bridge = brqfee5952c-2e
insecure=True

On the VCenter side (v6.5), inside Cluster01, I configured a "DSwitch" (with that name, not sure if relevant) with a Distributed Port Group named "brqfee5952c-2e". That bridge name corresponds to a public external network in my Openstack setup. I may be missing something here.

image description

image description

I'm trying to place a VM in the Openstack "public" network:

openstack server create   --flavor 1CPU-1GBRAM-3GBDISK --nic net-id=fee5952c-2e90-4ced-8889-14c5cd8de34d --image "xenial-cloud-01" --availability-zone DC01 vm14

This is the nova-compute.log I'm getting:

2017-02-09 03:43:15.797 3898 INFO nova.compute.claims [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Claim successful
2017-02-09 03:43:16.502 3898 INFO os_vif [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] Loaded VIF plugin class '<class 'vif_plug_ovs.ovs.OvsPlugin'>' with name 'ovs'
2017-02-09 03:43:16.504 3898 INFO os_vif [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] Loaded VIF plugin class '<class 'vif_plug_linux_bridge.linux_bridge.LinuxBridgePlugin'>' with name 'linux_bridge'
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Instance failed to spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Traceback (most recent call last):
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2078, in _build_resources
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     yield resources
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1920, in _build_and_run_instance
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     block_device_info=block_device_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/driver.py", line 316, in spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     admin_password, network_info, block_device_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py", line 739, in spawn
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     metadata)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vmops.py", line 281, in build_virtual_machine
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     network_info)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 178, in get_vif_info
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     is_neutron, vif))
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 164, in get_vif_dict
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     ref = get_network_ref(session, cluster, vif, is_neutron)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 153, in get_network_ref
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     network_ref = _get_neutron_network(session, cluster, vif)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]   File "/usr/lib/python2.7/dist-packages/nova/virt/vmwareapi/vif.py", line 147, in _get_neutron_network
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]     raise exception.InvalidInput(reason=reason)
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] InvalidInput: Invalid input received: vif type bridge not supported
2017-02-09 03:43:18.525 3898 ERROR nova.compute.manager [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0]
2017-02-09 03:43:18.535 3898 INFO nova.compute.manager [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Terminating instance
2017-02-09 03:43:18.703 3898 WARNING nova.virt.vmwareapi.vmops [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Instance does not exist on backend
2017-02-09 03:43:18.705 3898 INFO nova.compute.manager [req-3b883f16-cfab-4671-9102-d75b0d2b7d70 733a6742f1694192b187dcd3374db1c7 4f9ed2343f814823a1be6a40c58e8018 - - -] [instance: a04d3f86-2b84-4e3a-ac8a-04a4df5a69f0] Took 0.16 seconds to destroy the instance on the hypervisor.

Any clue?

Thanks!

Gianpietro