Comment 3 for bug 1891673

I have put a workaround for this issue here - https://gist.github.com/dosaboy/eca8dcd4560f68d856f465ca8382c58b

Note that this workaround is required even after the fix lands as the l3 agent will not be able to delete old allocations left behind by this bug.