nova-vmware with NSX-mh neutron plugin: instance not connected to network because network type set opaque which is invalid on ESXi

Bug #1649322 reported by Larry Michel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Confirmed
Undecided
Unassigned
vmware-nsx
Confirmed
Undecided
Unassigned

Bug Description

When nova-vmware is used as compute with NSX-mh neutron plugin, network type for launch OpenStack instance is being set to opaque, but that is not valid network type for the NSX vswitch. It should be nsx.network. As a result, instance is launched and remains disconnected.

If trying to create an NSX vswitch on ESXi, it shows opaque as invalid.

~ # nsxcli network/add br-int2 br-int2 opaque manual
Invalid opaque network type
Valid types are nsx.network and nsx-bridge.network
nsx-appctl: nsxd: server returned an error
~ #

This applies to both ESXi 5.5 and 6.0

Tags: vmware oil
Revision history for this message
Matt Riedemann (mriedem) wrote :

I'm not sure what this has to do with Nova, so I'm marking this as invalid for Nova.

Changed in nova:
status: New → Invalid
tags: added: vmware
Revision history for this message
Larry Michel (lmic) wrote :

@mriedem The issue is in nova/virt/vmwareapi/virt.py. This is where the network type is being set for the instance.

description: updated
summary: - NSX-mh: Invalid opaque network type
+ nova-vmware with NSX-mh neutron plugin: instance not connected to
+ network because network type set opaque which is invalid on ESXi
Changed in nova:
status: Invalid → New
Sean Dague (sdague)
Changed in nova:
status: New → Confirmed
Changed in vmware-nsx:
status: New → Confirmed
Revision history for this message
Adit Sarfaty (asarfaty) wrote :

The MH plugin is no linger supported, so this should be set as won't fix

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.