This looks like it's an issue where the devstack node may not have been clean when we started, possibly reused from another run, as otherwise there is nothing keystone should port conflict against.
This looks like it's an issue where the devstack node may not have been clean when we started, possibly reused from another run, as otherwise there is nothing keystone should port conflict against.