Comment 3 for bug 1798994

This is likely upstream openstack behavior. It's not likely that this is something unique to StarlingX.
If this is standard openstack behavior, we may choose not to change it. Further investigation is required.

I wouldn't mark this as stx.2018.10 gating -- it's a very specific test scenario. Marking as stx.2019.03 instead.