Hey Mikhail! That's exactly what was happening to us. Thank you very much for the super useful help!!
Steve On Fri, Mar 31, 2017 at 7:09 AM, Mikhail Medvedev <mihail...@gmail.com> wrote: > On Thu, Mar 30, 2017 at 4:04 PM, Sterdnot Shaken > <sterdnotsha...@gmail.com> wrote: > > Openstack version: Mitaka > > Number of external bridges: 1 > > > > Whenever I spawn a new cirros image, I'm get 2 ip's out of the same ip > block > > assigned to each instance. > > > > Anyone know why? > > I saw this happen on Mitaka cloud when an instance was rescheduled to > a different compute node. E.g. initial scheduling puts it on compute1, > it fails to boot there for some reason, and is being rescheduled to a > compute2. It already has a port assigned from first attempt, and gets > second port attached on reschedule, leaking the first port ip. > > To confirm if this is also what's happening in your case you can check > nova scheduler log on your controller. > > > > > Thanks! > > > > _______________________________________________ > > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > Post to : openstack@lists.openstack.org > > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/ > openstack > > > > --- > Mikhail Medvedev (mmedvede) > IBM >
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
