This is not a nova issue but a neutron issue. ** No longer affects: nova
-- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1290854 Title: Missing internal ovs vlan tag for a port of resumed instance Status in OpenStack Neutron (virtual network service): New Bug description: If we suspend and then resume an instance it becomes unreachable from the tenant network $nova boot --image 263f4823-f43c-4f2a-a845-2221f4a2dad1 --flavor 1 --nic net-id=61ade795-f123-4880-9ab5-a73e0c1b2e70 server1 $ ping 10.0.0.8 PING 10.0.0.8 (10.0.0.8) 56(84) bytes of data. 64 bytes from 10.0.0.8: icmp_req=1 ttl=63 time=46.5 ms 64 bytes from 10.0.0.8: icmp_req=2 ttl=63 time=0.675 ms 64 bytes from 10.0.0.8: icmp_req=3 ttl=63 time=0.572 ms $ nova suspend 9b55928f-e6c7-49b3-9480-0df926dc6a08 $ nova resume 9b55928f-e6c7-49b3-9480-0df926dc6a08 $ ping 10.0.0.8 PING 10.0.0.8 (10.0.0.8) 56(84) bytes of data. From 172.24.4.2 icmp_seq=1 Destination Host Unreachable From 172.24.4.2 icmp_seq=2 Destination Host Unreachable From 172.24.4.2 icmp_seq=3 Destination Host Unreachable ovs-vsctl shows that after resume the instanse's port lacks its VLAN tag before suspend: Port "tap69cb10fd-43" tag: 1 Interface "tap69cb10fd-43" after suspend: Port "tap69cb10fd-43" tag: 1 Interface "tap69cb10fd-43" after resume: Port "tap69cb10fd-43" Interface "tap69cb10fd-43" The reason of such behavior is due to the patch https://review.openstack.org/#/c/67981/7 which introduced removing and recreating of existing interfaces. What's more it seems that ovs-agent doesn't notice tag's disappearance and that's why it doesn't mark it as updated. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1290854/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
