I think this is a known issue in 2.0.x where, under certain conditions,
some IPs are still marked in use. It seems to be triggered by instance
not starting properly (but not only).

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in Ubuntu.
https://bugs.launchpad.net/bugs/676832

Title:
  "Ghost" instance using a slot + elastic IP

To manage notifications about this bug go to:
https://bugs.launchpad.net/eucalyptus/+bug/676832/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Reply via email to