We are no longer able to create new tenant networks after the 10.0.01 upgrade. We can create the tenant org and the tenant edges. But all attempts at a routed network will fail.
In the GUI we see the error "realization failed". I do see this error in the logs on the nodes. I have of course opened a ticket with VMWare but we are hoping for a any clues sooner than VMWare support tends to respond to tickets.
Anyone else seeing this?
- The input request is invalid.
- XStream unmarshalling exception; nested exception is com.thoughtworks.xstream.converters.ConversionException:
---- Debugging information ----
cause-exception : com.thoughtworks.xstream.security.ForbiddenClassException
cause-message : com.vmware.vshield.vsm.vdn.dto.HardwareGatewayBindingDto
class : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto
required-type : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto
converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
line number : 2
class[1] : com.vmware.vshield.vsm.dto.DataPage
class[2] : com.vmware.vshield.vsm.vdn.dto.VirtualWiresDto
version : not available
-------------------------------
-
---- Debugging information ----
cause-exception : com.thoughtworks.xstream.security.ForbiddenClassException
cause-message : com.vmware.vshield.vsm.vdn.dto.HardwareGatewayBindingDto
class : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto
required-type : com.vmware.vshield.vsm.vdn.dto.VirtualWireDto
converter-type : com.thoughtworks.xstream.converters.reflection.ReflectionConverter
line number : 2
class[1] : com.vmware.vshield.vsm.dto.DataPage
class[2] : com.vmware.vshield.vsm.vdn.dto.VirtualWiresDto
version : not available
-------------------------------
Yes, we're seeing this same problem. Unable to create new routed networks. vCD version 10.0.0.1. Just starting to investigate more in depth now..
Out of interest some questions:
- Which version of NSX are you using?
- Are you using NSX logical switch hardware bindings (hardware VXLAN gateways via OVSDB) ? (We're seeing some lines related to hw bindings in the log entries, but not totally sure if those are related to this problem or not).