Comment 4 for bug 1830108

Based on discussion with Kevin Smith, he confirmed that this doesn't appear to be a vim router rescheduling issue. It appears that the neutron l3 agent/neuron server is misbehaving.

Given that stx is currently using an older stein snapshot of neutron in a temporary fork, I'd like to see a re-test done once the docker images pointing to latest stein are built as part of the cengn May 27 evening build.

For reference, this commit updated the stx-neutron image build to point to the upstream neutron repo:
https://review.opendev.org/#/c/661015/