Nova seems to associate @crusnov with this server
Addresses data:

{
    'lan-flat-cloudinstances2b': [
        {
            'OS-EXT-IPS-MAC:mac_addr': 'fa:16:3e:8e:7d:5e',
            'version': 4,
            'addr': '172.16.6.244',
            'OS-EXT-IPS:type': 'fixed'
        },
        {
            'OS-EXT-IPS-MAC:mac_addr': 'fa:16:3e:f0:8e:7a',
            'version': 4,
            'addr': '172.16.6.245',
            'OS-EXT-IPS:type': 'fixed'
        }
    ]
}

@crusnov is this instance working at all? If not please could you try deleting it, and if needed, re-create?

@aborrero it looks like arturo-k8s-test-3.openstack.eqiad.wmflabs has also got this issue

This is an error that sometimes happens during VM creation -- I think it's something like...

1. VM is scheduled
2. IP is allocated by Neutron
3. Scheduled VM fails to come up (possibly due to a cloudvirt being offline)
4. VM is rescheduled
5. IP is allocated by Neutron

etc.

As far as I know it only happens to brand new VMs so never damages any actual work in progress. And I don't know if the bug is still present in Newton.

Probably best to just delete the affected VM and wait and see if it happens again.