Wrap checks after deletes in a WUKS 69/77869/3
authorJamo Luhrsen <jluhrsen@redhat.com>
Fri, 16 Nov 2018 06:40:35 +0000 (22:40 -0800)
committerSam Hague <shague@redhat.com>
Fri, 16 Nov 2018 18:10:06 +0000 (18:10 +0000)
commita5855e7099fa438598154f8ac2102247a2f8ce8d
tree326ef0ce1db4547467b4b22885420e270e90a261
parent6161209993d3f12b70432013ff69f7ce1eda78b5
Wrap checks after deletes in a WUKS

Example here shows that a delete was done but the
uuid still showed up in the config store. In the
example below, you can see the openstack CLI to
delete the l2gw connection completed at timestamp
00:39. Looking in the 3 karaf logs (it's a cluster
job) you can see the delete made it by 00:41 or
00:42 depending on which log you check. So, polling
for up to 5 seconds should give a little time for
that to propagate.

example:
https://logs.opendaylight.org/releng/vex-yul-odl-jenkins-1/builder-copy-sandbox-logs/508/jamo-netvirt-csit-hwvtep-3node-0cmb-1ctl-2cmp-openstack-queens-upstream-stateful-fluorine/14/robot-plugin/log_full.html.gz#s1-s1-s1-t20-k1-k4

Change-Id: I4e09db3a03a4851df14d47b5328abe7eba834052
Signed-off-by: Jamo Luhrsen <jluhrsen@redhat.com>
csit/libraries/L2GatewayOperations.robot