In MANAGED mode, removing public ip address blocks needs a cloud restart
| 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-
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-
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 | #1 |
| 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 | #2 |
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.