[NETVIRT-267] Empty security groups OF tables after restarting ODL and deleting some files from inventory Created: 13/Nov/16  Updated: 03/May/18  Resolved: 06/Jul/17

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Mickael Strock-Vidal Assignee: Aswin Suryanarayanan
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7164

 Description   

Overview:
---------
On working devstack (i.e. ping works from VM to VM on internal network) restarting ODL caused security groups tables (41, 42) to be empty

Steps:
------

  • Load devstack
  • Create networks, VMs
  • Check ping connectivity
  • Restart ODL (see below what is included in restarting the ODL)
  • Delete networks, VMs
  • Create networks, VMs
  • Check ping connectivity

Expected Results:
-----------------

  • Ping connectivity exists after restarting the ODL

Actual results:
---------------

  • No ping between VMs

Logs:

Local in centos-devel/mnt/mpr-dev/pub/Mickael/[bug-id]

 Comments   
Comment by Mickael Strock-Vidal [ 13/Nov/16 ]

As mentioned here are more details on the restart procedure of the ODL:

Stop:
/opt/stack/opendaylight/distribution-karaf-'${ODL_VERSION}'/bin/stop;
sleep 10 ;
pkill -f opendaylight
sudo rm -f \$(readlink -f /home/stack/logs/screen-karaf.log) ;
rm rf /opt/stack/opendaylight/distribution-karaf${ODL_VERSION}/journal /opt/stack/opendaylight/distribution-karaf-${ODL_VERSION}/snapshots
sudo rm -f /opt/stack/logs/screen-karaf.log* ;
rm rf /opt/stack/opendaylight/distribution-karaf${ODL_VERSION}/data/cache
sudo ovs-vsctl del-br br-int

Start:
/opt/stack/opendaylight/distribution-karaf-${ODL_VERSION}/bin/start

Comment by Mickael Strock-Vidal [ 13/Nov/16 ]

Zan has tested it with a simple restart including this actions only:
/opt/stack/opendaylight/distribution-karaf-'${ODL_VERSION}'/bin/stop;
sleep 10 ;
pkill -f opendaylight
/opt/stack/opendaylight/distribution-karaf-${ODL_VERSION}/bin/start

and issue wasn't encounter.
Issue is still relevant since the creation of networks, subnets, VMs after the ODL restart as I did it should have recreate the different OF rules required to handle the scenario

Comment by Slava Radune [ 20/Dec/16 ]

This is not SG bug.
Indeed there is no ping.
When I tested it I created following:
1. Network.
2. VM1 in this network on compute1 (that runs on same vm1 as controller)
3. VM2 in this network on compute2 (that runs on different vm2)

VM2 didn't get IP.
When trying to send dhcp request from VM2 to qdhcp service that runs on vm1.
But the packet doesn't leave the ovs because it is dropped in table 55:

cookie=0x8800007, duration=2237.667s, table=55, n_packets=22, n_bytes=4380, priority=10,tun_id=0x7,metadata=0x70000000000/0x1fffff0000000000 actions=drop

Comment by Slava Radune [ 20/Dec/16 ]

This is not SG bug.
Indeed there is no ping.
When I tested it I created following:
1. Network.
2. VM1 in this network on compute1 (that runs on same vm1 as controller)
3. VM2 in this network on compute2 (that runs on different vm2)

VM2 didn't get IP.
When trying to send dhcp request from VM2 to qdhcp service that runs on vm1.
But the packet doesn't leave the ovs because it is dropped in table 55:

cookie=0x8800007, duration=2237.667s, table=55, n_packets=22, n_bytes=4380, priority=10,tun_id=0x7,metadata=0x70000000000/0x1fffff0000000000 actions=drop

Generated at Wed Feb 07 20:21:07 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.