To be more precise, it's coming from rev774 on clc/modules/msgs/src/main/java/com/eucalyptus/util/NetworkUtil.java: http://bazaar.launchpad.net/~eucalyptus-maintainers/eucalyptus/1.6/revision/774#clc/modules/msgs/src/main/java/com/eucalyptus/util/NetworkUtil.java It was a fix for bug 431934, the fact that it worked was indeed a bug.
** Summary changed: - euca_conf --register-walrus localhost fails in 1.6~bzr808 + Autoregister runs euca_conf --register-walrus localhost but that is refused in 1.6~bzr808 ** Summary changed: - Autoregister runs euca_conf --register-walrus localhost but that is refused in 1.6~bzr808 + Autoregister runs euca_conf with "localhost" but that is refused in 1.6~bzr808 ** Description changed: - "euca_conf --register-walrus localhost" is the recommended way to - register a Walrus on a local cloud+cluster controller setup (and is also - used by the initscript themselves to provide autoregister). - - Works with 1.6~bzr746-0ubuntu3. + register_local_cloud in the initscripts tries (for example) "euca_conf --register-walrus localhost" to register components. + It used to work in 1.6~bzr746-0ubuntu3. With 1.6~bzr808-0ubuntu1, it fails with the following error: Components cannot be registered using local, link-local, or multicast addresses. + + We need to find a way to autoregister components with the correct + external IP address, or drop autoregistering altogether. -- Autoregister runs euca_conf with "localhost" but that is refused in 1.6~bzr808 https://bugs.launchpad.net/bugs/434593 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in ubuntu. -- 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
