# After vm snapshot / revert, vlan does not get (re-)tagged on openvswitch

**URL:** <https://forum.opennebula.io/t/after-vm-snapshot-revert-vlan-does-not-get-re-tagged-on-openvswitch/5237>\
**Category:** Product Support\
**Created:** [November 7, 2017, 1:51pm UTC](https://forum.opennebula.io/t/after-vm-snapshot-revert-vlan-does-not-get-re-tagged-on-openvswitch/5237 "2017-11-07T13:51:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gklepach](https://avatars.discourse-cdn.com/v4/letter/g/d07c76/32.png) [@gklepach](https://forum.opennebula.io/u/gklepach)\
**Post date:** [November 7, 2017, 1:51pm UTC](https://forum.opennebula.io/t/after-vm-snapshot-revert-vlan-does-not-get-re-tagged-on-openvswitch/5237/1 "2017-11-07T13:51:10Z")

</div>

_Versions of the related components and OS (frontend, hypervisors, VMs):_  
ONE 5.4.1 on CentOS 7.4.1708  
Host on CentOS 7.4.1708  
VM on CentOS 7.4.1708

_Steps to reproduce:_

1. Check config of ovs on host with VM (ovs-vsctl show)  
( Port "one-101-0"  
**tag: 103**  
Interface “one-101-0”)

2. Create snap of VM

3. Revert from snap

_Current results:_  
( Port "one-101-0"  
Interface “one-101-0”)  
**VM is not pinging**

_Expected results:_  
( Port "one-101-0"  
**tag: 103**  
Interface “one-101-0”)  
**VM is pinging**

_Workaround 1_  
start “sudo ovs-vsctl set Port one-101-0 tag=103”

_Workaround 2_  
shutdown vm, and start it, after start we see configuring of ovs. ()

_p.s._  
Link to bag on [https://dev.opennebula.org/issues/3937](https://dev.opennebula.org/issues/3937), it,s closed, but not fixed.