| 2009-10-23 09:19:45 |
Nick Barcet |
bug |
|
|
added bug |
| 2009-10-23 09:25:19 |
Nick Barcet |
summary |
dding nodes in several waves after launching VMs is not possible |
Adding nodes in several waves after launching VMs is not possible |
|
| 2009-10-26 09:59:41 |
Thierry Carrez |
eucalyptus (Ubuntu): importance |
Undecided |
High |
|
| 2009-10-26 20:33:02 |
Mathias Gug |
eucalyptus (Ubuntu): status |
New |
Confirmed |
|
| 2009-10-27 19:16:22 |
Mathias Gug |
nominated for series |
|
Ubuntu Karmic |
|
| 2009-10-27 19:16:22 |
Mathias Gug |
bug task added |
|
eucalyptus (Ubuntu Karmic) |
|
| 2009-10-27 21:01:05 |
Mathias Gug |
branch linked |
|
lp:~mathiaz/eucalyptus/k-find-cluster-multi-ip-fix |
|
| 2009-10-27 22:32:40 |
Mathias Gug |
eucalyptus (Ubuntu Karmic): assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-10-28 00:12:39 |
Steve Langasek |
eucalyptus (Ubuntu Karmic): milestone |
|
ubuntu-9.10 |
|
| 2009-10-28 00:38:29 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): status |
Confirmed |
Triaged |
|
| 2009-10-28 01:06:25 |
Matt Zimmerman |
summary |
Adding nodes in several waves after launching VMs is not possible |
When installing a node, euca_find_cluster fails to locate the cluster controller if instances are running |
|
| 2009-10-28 02:30:56 |
Matt Zimmerman |
bug task added |
|
ubuntu-release-notes |
|
| 2009-10-28 02:31:20 |
Matt Zimmerman |
ubuntu-release-notes: assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-10-28 02:31:38 |
Matt Zimmerman |
ubuntu-release-notes: status |
New |
Triaged |
|
| 2009-10-28 02:31:42 |
Matt Zimmerman |
ubuntu-release-notes: importance |
Undecided |
Medium |
|
| 2009-10-28 02:31:47 |
Matt Zimmerman |
eucalyptus (Ubuntu Karmic): milestone |
ubuntu-9.10 |
karmic-updates |
|
| 2009-10-28 17:07:22 |
Mathias Gug |
description |
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 |
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:
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 conduct 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.
================== |
|
| 2009-10-28 17:07:56 |
Mathias Gug |
description |
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:
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 conduct 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.
================== |
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:
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.
================== |
|
| 2009-10-28 17:08:11 |
Mathias Gug |
ubuntu-release-notes: status |
Triaged |
In Progress |
|
| 2009-10-28 17:10:53 |
Mathias Gug |
ubuntu-release-notes: status |
In Progress |
Fix Committed |
|
| 2009-10-28 17:21:26 |
Mathias Gug |
description |
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:
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.
================== |
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.
================== |
|
| 2009-10-29 11:27:50 |
Steve Langasek |
ubuntu-release-notes: status |
Fix Committed |
Fix Released |
|
| 2009-10-30 21:46:59 |
Mathias Gug |
bug task added |
|
avahi (Ubuntu) |
|
| 2009-10-30 21:47:13 |
Mathias Gug |
avahi (Ubuntu Karmic): status |
New |
Triaged |
|
| 2009-10-30 21:47:17 |
Mathias Gug |
avahi (Ubuntu Karmic): importance |
Undecided |
High |
|
| 2009-10-30 21:47:21 |
Mathias Gug |
avahi (Ubuntu Karmic): assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-10-30 21:47:25 |
Mathias Gug |
avahi (Ubuntu Karmic): milestone |
|
karmic-updates |
|
| 2009-10-30 21:55:16 |
Launchpad Janitor |
branch linked |
|
lp:~mathiaz/ubuntu/karmic/avahi/k-eucalyptus-conf-support |
|
| 2009-10-30 21:56:26 |
Mathias Gug |
eucalyptus (Ubuntu): milestone |
karmic-updates |
|
|
| 2009-10-30 21:57:09 |
Launchpad Janitor |
branch linked |
|
lp:~mathiaz/eucalyptus/k-eucalyptus-conf-support |
|
| 2009-10-30 23:01:57 |
Mathias Gug |
avahi (Ubuntu Karmic): status |
Triaged |
In Progress |
|
| 2009-10-30 23:02:06 |
Mathias Gug |
eucalyptus (Ubuntu Karmic): status |
Triaged |
In Progress |
|
| 2009-10-30 23:02:14 |
Mathias Gug |
eucalyptus (Ubuntu): assignee |
Mathias Gug (mathiaz) |
|
|
| 2009-11-03 16:28:48 |
Mathias Gug |
description |
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.
================== |
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.
==================
Avahi SRU
Impact:
Public IPs are added to the Cluster Controller (CC) when instances are booted. These IPs are then automatically published by the avahi-daemon running on the CC. The instance public IPs should not be resolvable via avahi.
How the bug has been addressed:
The default avahi-daemon upstart job has been modified to use /etc/eucalyptus/avahi-daemon.conf (which will be shipped by the eucalyptus package) as the configuration file instead of the default configuration file.
To reproduce the bug:
1. Install avahi-daemon and make sure it's started with the default configuration file (ie no configuration file specified on the command line) - both an a new install and on upgrades.
2. Move /etc/avahi/avahi-daemon.conf to /etc/eucalyptus/avahi-daemon.conf and restart avahi-daemon. Make sure the process has been restarted and running with the new eucalyptus avahi-daemon configuration file.
Regression potential:
eucalyptus is not installed by default - avahi-daemon should just restart normally. On existing eucalyptus Cluster Controllers, resolution via avahi for the CC will not work until the eucalyptus-cc-publication-ip job has started.
================== |
|
| 2009-11-03 16:38:34 |
Mathias Gug |
description |
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.
==================
Avahi SRU
Impact:
Public IPs are added to the Cluster Controller (CC) when instances are booted. These IPs are then automatically published by the avahi-daemon running on the CC. The instance public IPs should not be resolvable via avahi.
How the bug has been addressed:
The default avahi-daemon upstart job has been modified to use /etc/eucalyptus/avahi-daemon.conf (which will be shipped by the eucalyptus package) as the configuration file instead of the default configuration file.
To reproduce the bug:
1. Install avahi-daemon and make sure it's started with the default configuration file (ie no configuration file specified on the command line) - both an a new install and on upgrades.
2. Move /etc/avahi/avahi-daemon.conf to /etc/eucalyptus/avahi-daemon.conf and restart avahi-daemon. Make sure the process has been restarted and running with the new eucalyptus avahi-daemon configuration file.
Regression potential:
eucalyptus is not installed by default - avahi-daemon should just restart normally. On existing eucalyptus Cluster Controllers, resolution via avahi for the CC will not work until the eucalyptus-cc-publication-ip job has started.
================== |
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.
==================
Avahi SRU
Impact:
Public IPs are added to the Cluster Controller (CC) when instances are booted. These IPs are then automatically published by the avahi-daemon running on the CC. The instance public IPs should not be resolvable via avahi.
How the bug has been addressed:
The default avahi-daemon upstart job has been modified to use /etc/eucalyptus/avahi-daemon.conf (which will be shipped by the eucalyptus package) as the configuration file instead of the default configuration file.
To reproduce the bug:
1. Install avahi-daemon and make sure it's started with the default configuration file (ie no configuration file specified on the command line - the process should use the hostname) - both an a new install and on upgrades:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 1373 1 0 11:30 ? 00:00:00 avahi-daemon: running [t-avahi.local]
avahi 1375 1373 0 11:30 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 1422 977 0 11:31 pts/0 00:00:00 grep avahi
2. Copy /etc/avahi/avahi-daemon.conf to /etc/eucalyptus/avahi-daemon.conf and edit /etc/eucalyptus/avahi-daemon.conf to change the published hostname to eucalyptus. Restart avahi-daemon. Make sure the process has been restarted and running with the new eucalyptus avahi-daemon configuration file:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 2070 1 1 11:35 ? 00:00:00 avahi-daemon: running [eucalyptus.local]
avahi 2071 2070 0 11:35 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 2073 977 0 11:35 pts/0 00:00:00 grep avahi
Regression potential:
eucalyptus is not installed by default - avahi-daemon should just restart normally. On existing eucalyptus Cluster Controllers, resolution via avahi for the CC will not work until the eucalyptus-cc-publication-ip job has started.
================== |
|
| 2009-11-03 21:58:15 |
Mathias Gug |
description |
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.
==================
Avahi SRU
Impact:
Public IPs are added to the Cluster Controller (CC) when instances are booted. These IPs are then automatically published by the avahi-daemon running on the CC. The instance public IPs should not be resolvable via avahi.
How the bug has been addressed:
The default avahi-daemon upstart job has been modified to use /etc/eucalyptus/avahi-daemon.conf (which will be shipped by the eucalyptus package) as the configuration file instead of the default configuration file.
To reproduce the bug:
1. Install avahi-daemon and make sure it's started with the default configuration file (ie no configuration file specified on the command line - the process should use the hostname) - both an a new install and on upgrades:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 1373 1 0 11:30 ? 00:00:00 avahi-daemon: running [t-avahi.local]
avahi 1375 1373 0 11:30 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 1422 977 0 11:31 pts/0 00:00:00 grep avahi
2. Copy /etc/avahi/avahi-daemon.conf to /etc/eucalyptus/avahi-daemon.conf and edit /etc/eucalyptus/avahi-daemon.conf to change the published hostname to eucalyptus. Restart avahi-daemon. Make sure the process has been restarted and running with the new eucalyptus avahi-daemon configuration file:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 2070 1 1 11:35 ? 00:00:00 avahi-daemon: running [eucalyptus.local]
avahi 2071 2070 0 11:35 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 2073 977 0 11:35 pts/0 00:00:00 grep avahi
Regression potential:
eucalyptus is not installed by default - avahi-daemon should just restart normally. On existing eucalyptus Cluster Controllers, resolution via avahi for the CC will not work until the eucalyptus-cc-publication-ip job has started.
================== |
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.
==================
Avahi SRU
Impact:
Public IPs are added to the Cluster Controller (CC) when instances are booted. These IPs are then automatically published by the avahi-daemon running on the CC. The instance public IPs should not be resolvable via avahi.
How the bug has been addressed:
The default avahi-daemon upstart job has been modified to use /etc/eucalyptus/avahi-daemon.conf (which will be shipped by the eucalyptus package) as the configuration file instead of the default configuration file.
To reproduce the bug:
1. Install avahi-daemon and make sure it's started with the default configuration file (ie no configuration file specified on the command line - the process should use the hostname) - both an a new install and on upgrades:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 1373 1 0 11:30 ? 00:00:00 avahi-daemon: running [t-avahi.local]
avahi 1375 1373 0 11:30 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 1422 977 0 11:31 pts/0 00:00:00 grep avahi
2. Copy /etc/avahi/avahi-daemon.conf to /etc/eucalyptus/avahi-daemon.conf and edit /etc/eucalyptus/avahi-daemon.conf to change the published hostname to eucalyptus. Restart avahi-daemon. Make sure the process has been restarted and running with the new eucalyptus avahi-daemon configuration file:
mathiaz@t-avahi:~$ ps -ef | grep avahi
avahi 2070 1 1 11:35 ? 00:00:00 avahi-daemon: running [eucalyptus.local]
avahi 2071 2070 0 11:35 ? 00:00:00 avahi-daemon: chroot helper
mathiaz 2073 977 0 11:35 pts/0 00:00:00 grep avahi
Regression potential:
eucalyptus is not installed by default - avahi-daemon should just restart normally. On existing eucalyptus Cluster Controllers, resolution via avahi for the CC will not work until the eucalyptus-cc-publication-ip job has started.
==================
eucalyptus sru
Impact:
Adding new Node Controllers by installing them via the -server ISO will fail if instances with public IPs are running. This is due to the fact that public IPs are added on the Cluster Controller whose avahi-daemon will automatically publish. Since the installer relies on Avahi resolution to find the IP address of the Cluster Controller, the install will fail while trying to download the preseed file from the last public IP added to the CC.
How the bug has been addressed:
A specific avahi daemon configuration has been added that will not publish addresses by default - instead a specific upstart job has been added that will publish the CC IPs.
To reproduce the bug:
1. Install a Cluster Controller and one Node Controller. Start an instance with a public IP and note its public IP.
2. Boot from the -server iso and select to install an Ubuntu Entreprise Cloud.
3. Before the update, the installation process will fail with an error message stating that the preseed file cannot be downloaded from the public IP address of the instance.
4. After the update on the CC, the installation process is successful (ie the preseed file is correctly downloaded from the CC IP).
Regression potential:
The avahi-daemon running on the CC will stop publishing any IP addresses configured on any interfaces from the CC. Connection from a local network relying on avahi dns resolution will be broken. Note that it only affects system which have the eucalyptus-cc package installed.
================== |
|
| 2009-11-03 22:50:40 |
Mathias Gug |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-11-03 23:14:53 |
Steve Langasek |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
In Progress |
|
| 2009-11-03 23:47:21 |
Martin Pitt |
avahi (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-11-03 23:47:27 |
Martin Pitt |
tags |
|
verification-needed |
|
| 2009-11-03 23:48:13 |
Martin Pitt |
avahi (Ubuntu): status |
New |
Incomplete |
|
| 2009-11-03 23:48:33 |
Martin Pitt |
avahi (Ubuntu): assignee |
|
Mathias Gug (mathiaz) |
|
| 2009-11-04 01:54:47 |
Mathias Gug |
avahi (Ubuntu): importance |
Undecided |
Low |
|
| 2009-11-04 01:54:47 |
Mathias Gug |
avahi (Ubuntu): status |
Incomplete |
Won't Fix |
|
| 2009-11-05 17:51:43 |
Mathias Gug |
tags |
verification-needed |
uec verification-needed |
|
| 2009-11-06 03:15:30 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/avahi |
|
| 2009-11-06 10:06:54 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
In Progress |
Fix Committed |
|
| 2009-11-06 11:00:25 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/karmic-proposed/eucalyptus |
|
| 2009-11-06 13:58:49 |
Thierry Carrez |
tags |
uec verification-needed |
uec verification-failed |
|
| 2009-11-10 20:18:09 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu-karmic |
|
| 2009-11-10 20:20:07 |
Dustin Kirkland |
attachment added |
|
out http://launchpadlibrarian.net/35497155/out |
|
| 2009-11-13 08:19:40 |
Martin Pitt |
tags |
uec verification-failed |
uec verification-failed verification-needed |
|
| 2009-11-13 17:22:13 |
Martin Pitt |
tags |
uec verification-failed verification-needed |
uec verification-needed |
|
| 2009-11-20 13:15:19 |
Martin Pitt |
tags |
uec verification-needed |
uec verification-done |
|
| 2009-11-23 09:38:23 |
Launchpad Janitor |
avahi (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-11-23 09:46:08 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-11-23 09:48:46 |
Martin Pitt |
eucalyptus (Ubuntu): status |
Triaged |
Fix Released |
|
| 2009-11-23 09:52:13 |
Martin Pitt |
eucalyptus (Ubuntu Karmic): status |
Fix Released |
Fix Committed |
|
| 2009-11-26 17:34:56 |
Colin Watson |
eucalyptus (Ubuntu): status |
Fix Released |
Triaged |
|
| 2009-11-26 17:34:56 |
Colin Watson |
eucalyptus (Ubuntu): assignee |
|
Colin Watson (cjwatson) |
|
| 2009-11-26 17:36:11 |
Colin Watson |
eucalyptus (Ubuntu): status |
Triaged |
Fix Committed |
|
| 2009-11-26 17:37:08 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-core-dev/eucalyptus/ubuntu |
|
| 2009-11-30 20:16:09 |
Launchpad Janitor |
eucalyptus (Ubuntu Karmic): status |
Fix Committed |
Fix Released |
|
| 2009-12-04 10:27:03 |
Colin Watson |
eucalyptus (Ubuntu): status |
Fix Committed |
Fix Released |
|
