** Description changed: Paul Gyermonprez from Intel, reported the following bug for which I do not have the necessary hw to try to reproduce: Adding nodes in several waves after launching VMs is not possible : 1. The “node mode” is discovered and the step is hanging 2. This step is the automatic preseed 3. But the answer from the server (via avahi ?) is sending a link to a wrong IP. 4. This wrong IP is the last one added to the eth interface.and the last one is the vlan used for VM communication Workaround : add ALL nodes before you launch the first VM Or close all VMs and make sure the only IPv4 for your eth is the one you want ================== Karmic Release notes: + + UEC Node Controller installation failure in an existing UEC Extending an existing Ubuntu Enterprise Cloud may fail during node controller installation started from the ISO with the "Install Ubuntu Enterprise Cloud" option. The Node installation fails with an error message stating that the preseed file cannot be downloaded from the Cluster Controller as the wrong IP address is used to connect to the Cluster Controller. The workaround is to perform a standard package installation rather than an ISO installation: Install a default Karmic server and then install the eucalyptus-nc package. Additionally the system's primary ethernet interface needs to be configured as a bridge and the Cloud Controller's eucalyptus user's public ssh key needs to be copied into the Node Controller's eucalyptus user's authorized_keys file. More detailed steps can be found in the UEC Package Install tutorial, Step 3 at https://help.ubuntu.com/community/UEC/PackageInstall. ==================
-- When installing a node, euca_find_cluster fails to locate the cluster controller if instances are running https://bugs.launchpad.net/bugs/458904 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
