Activity log for bug #1649322

Date Who What changed Old value New value Message
2016-12-12 16:09:58 Larry Michel bug added bug
2017-03-03 10:57:58 Larry Michel bug task added nova
2017-03-14 00:24:30 Matt Riedemann nova: status New Invalid
2017-03-14 00:24:49 Matt Riedemann tags oil oil vmware
2017-03-14 05:20:52 Larry Michel description For NSX-mh, network type is being set to opaque, but that does not appear to be valid. 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 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
2017-03-14 05:20:56 Larry Michel 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
2017-03-14 05:21:03 Larry Michel nova: status Invalid New
2017-06-28 15:40:32 Sean Dague nova: status New Confirmed
2017-06-28 15:40:34 Sean Dague vmware-nsx: status New Confirmed