In MANAGED mode, removing public ip address blocks needs a cloud restart

Bug #444889 reported by Neil Soman on 2009-10-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eucalyptus
Triaged
Low
chris grzegorczyk

Bug Description

I changed VNET_PUBLICIPS
and restarted CCs. I had to restart the CLC for the old
addresses to not show up anymore.

before CLC restart

$ euca-describe-addresses
ADDRESS 192.168.7.113 nobody
ADDRESS 192.168.7.114 nobody
ADDRESS 192.168.7.115 nobody
ADDRESS 192.168.7.116 nobody
ADDRESS 192.168.7.120 nobody
ADDRESS 192.168.7.121 nobody
ADDRESS 192.168.7.160 nobody
ADDRESS 192.168.7.161 nobody
ADDRESS 192.168.7.162 nobody
ADDRESS 192.168.7.163 nobody
ADDRESS 192.168.7.164 nobody
ADDRESS 192.168.7.165 nobody

after CLC restart (expected).

$ euca-describe-addresses
ADDRESS 192.168.7.160 nobody
ADDRESS 192.168.7.161 nobody
ADDRESS 192.168.7.162 nobody
ADDRESS 192.168.7.163 nobody
ADDRESS 192.168.7.164 nobody
ADDRESS 192.168.7.165 nobody

Related branches

chris grzegorczyk (chris-grze) wrote :

Note that this is only true if you remove netblocks. Adding them works just fine. Its not clear that having the netblocks dissappear is a desirable behaviour. Neither is having to HUP eucalyptus-cloud.

Changed in eucalyptus:
status: New → Triaged
importance: Undecided → Low
assignee: nobody → chris grzegorczyk (chris-grze)
summary: - In MANAGED mode, changing public ip address blocks needs a cloud restart
+ In MANAGED mode, removing public ip address blocks needs a cloud restart
Andy Grimm (agrimm) wrote :

This issue is now being tracked upstream at http://eucalyptus.atlassian.net/browse/EUCA-2663

Please watch that issue for further updates.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers