2014-10-16 06:15:20 |
ZongKai LI |
description |
boot more several instances, create a floatingip, when re-assign the floatingip to multi instances, nova list will show incorrect result.
>>>neutron floatingip-associate floatingip-id instance-id-0
>>>neutron floatingip-associate floatingip-id instance-id-1
>>>neutron floatingip-associate floatingip-id instance-id-2
>>>nova list
(nova list result will be like:)
--------------------------
instance0 fixedip0, floatingip
instance1 fixedip1, floatingip
instance2 fixedip2, floatingip
instance0,1,2, they all have floatingip, but run "neutron floatingip-list", we can see it only bind to instance2.
another situation is that after a few time(half a min, or longer), "nova list" can show correct result.
---------------------------
instance0 fixedip0
instance1 fixedip1
instance2 fixedip2, floatingip |
boot more several instances, create a floatingip, when re-assign the floatingip to multi instances, nova list will show incorrect result.
>>>neutron floatingip-associate floatingip-id instance0-pord-id
>>>neutron floatingip-associate floatingip-id instance1-port-id
>>>neutron floatingip-associate floatingip-id instance2-port-id
>>>nova list
(nova list result will be like:)
--------------------------
instance0 fixedip0, floatingip
instance1 fixedip1, floatingip
instance2 fixedip2, floatingip
instance0,1,2, they all have floatingip, but run "neutron floatingip-list", we can see it only bind to instance2.
another situation is that after a few time(half a min, or longer), "nova list" can show correct result.
---------------------------
instance0 fixedip0
instance1 fixedip1
instance2 fixedip2, floatingip |
|