OVS Bridge Config missing Port VLAN after reverting Snapshot

We are running OpenNebula 5.8.1 on Centos 7.6.1810
using “open vSwitch Networking Mode”.
OpenvSwitch Version:
ovs-vsctl (Open vSwitch) 2.9.0
DB Schema 7.15.1

Problem description:
If we take a Snapshot from the VM and try to “REVERT” the
VM it looses the network connection.
The only way to get it working again is to undeploy/deploy the VM again.
It seems that the SNAPSHOT-Revert action breaks the running
ovs config.

OVS Port Info before Snapshot-Revert


ovs-vsctl list port one-50-0

_uuid : 2f6d9e9d-0128-4f8b-947c-8df5eb4c209c
bond_active_slave : []
bond_downdelay : 0
bond_fake_iface : false
bond_mode : []
bond_updelay : 0
cvlans : []
external_ids : {}
fake_bridge : false
interfaces : [68591da0-7f86-4019-9bff-748feb37a9c9]
lacp : []
mac : []
name : “one-50-0”
other_config : {}
protected : false
qos : []
rstp_statistics : {}
rstp_status : {}
statistics : {}
status : {}
tag : 103
trunks : []
vlan_mode : []

OVS Port Info after Snapshot-Revert


ovs-vsctl list port one-50-0

_uuid : 06de0b1f-3421-4a39-b05f-18084c53fd0a
bond_active_slave : []
bond_downdelay : 0
bond_fake_iface : false
bond_mode : []
bond_updelay : 0
cvlans : []
external_ids : {}
fake_bridge : false
interfaces : [2bc80c5a-f759-4b04-b10c-aa81e351e4ff]
lacp : []
mac : []
name : “one-50-0”
other_config : {}
protected : false
qos : []
rstp_statistics : {}
rstp_status : {}
statistics : {}
status : {}
tag : []
trunks : []
vlan_mode : []

VM LOG from Revert-Action


Mon Jun 3 14:29:20 2019 [Z0][VM][I]: New LCM state is HOTPLUG_SNAPSHOT
Mon Jun 3 14:29:24 2019 [Z0][VMM][I]: VM Snapshot successfully reverted.
Mon Jun 3 14:29:24 2019 [Z0][VM][I]: New LCM state is RUNNING

VM LOG SNAP from Deploy-Action


Mon Jun 3 14:32:39 2019 [Z0][VMM][I]: Generating deployment file: /var/lib/one/vms/50/deployment.5
Mon Jun 3 14:32:41 2019 [Z0][VMM][I]: Successfully execute transfer manager driver operation: tm_context.
Mon Jun 3 14:32:41 2019 [Z0][VMM][I]: ExitCode: 0
Mon Jun 3 14:32:41 2019 [Z0][VMM][I]: Successfully execute network driver operation: pre.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: Successfully execute virtualization driver operation: deploy.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: post: Executed “sudo ovs-vsctl set Port one-50-0 tag=103”.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: post: Executed “sudo ovs-ofctl del-flows VMSWITCH in_port=33”.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: post: Executed “sudo ovs-ofctl add-flow VMSWITCH ‘table=0,in_port=33,priority=100,actions=note:00.00.00.32.00.00,resubmit(,10)’”.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: post: Executed “sudo ovs-ofctl add-flow VMSWITCH ‘table=10,in_port=33,priority=100,actions=resubmit(,20)’”.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: post: Executed “sudo ovs-ofctl add-flow VMSWITCH ‘table=20,in_port=33,priority=100,actions=normal’”.
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: ExitCode: 0
Mon Jun 3 14:32:42 2019 [Z0][VMM][I]: Successfully execute network driver operation: post.
Mon Jun 3 14:32:42 2019 [Z0][VM][I]: New LCM state is RUNNING

Maybe it’s related to After vm snapshot / revert, vlan does not get (re-)tagged on openvswitch

BR
Stefan