eucalyptus (1.6.1~bzr1083-0ubuntu1) lucid; urgency=low
[ Dustin Kirkland ]
* Merge upstream bzr revision 1082; the following bugs have been fixed
upstream since the last merge:
- LP: #378969 - private bug
- LP: #404842 - init script fix
- LP: #434283 - existing keys should be
This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu7.3
---
eucalyptus (1.6~bzr931-0ubuntu7.3) karmic-proposed; urgency=low
* debian/eucalyptus-cc.postinst: restart avahi daemon so that it uses
eucalyptus specific configuration file (LP: #458904).
*
Reopening for Lucid as we want to fix this a different way there (with
an explicit TXT record).
** Changed in: eucalyptus (Ubuntu)
Status: Fix Released = Triaged
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Colin Watson (cjwatson)
** Changed in: eucalyptus (Ubuntu)
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu
--
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
Server Team, which is
This bug was fixed in the package eucalyptus - 1.6~bzr931-0ubuntu7.3
---
eucalyptus (1.6~bzr931-0ubuntu7.3) karmic-proposed; urgency=low
* debian/eucalyptus-cc.postinst: restart avahi daemon so that it uses
eucalyptus specific configuration file (LP: #458904).
*
I copied the karmic-proposed package to lucid. Ffor karmic-updates it is
still missing two verifications.
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Fix Released
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Fix Released = Fix Committed
--
When installing a node,
** Tags added: verification-done
** Tags removed: verification-needed
--
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
Server
Accepted eucalyptus into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
** Tags removed: verification-failed
--
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
Server Team, which is subscribed to
Tested 7.3 upgrade and everything works as expected. New instances with
public IPs will not change the address resolution.
--
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
This is now working, *but* upgrading to the latest package is not enough
to fix it on a running system. You need to restart avahi-daemon (to make
it pick up the new avahi-daemon.conf) before you restart eucalyptus (and
the publication takes place). Rebooting would also work, as it would
restart
Right. However the eucalyptus update should be applied at the same time
as the avahi-daemon update. In such a scenario the daemon will be
restarted by the avahi-daemon ugprade and the new configuration file
should be picked up. I'll test this use case and report back.
--
When installing a node,
Ok - that doesn't work either: conffiles are installed during the
configuration step (before postinst is called) rather than then the
unpack phase. As such eucalyptus specific avahi configuration file is
not available when avahi-daemon is restarted by avahi-daemon postinstall
script.
avahi-daemon
** Branch linked: lp:~ubuntu-core-dev/eucalyptus/ubuntu-karmic
--
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
Server Team,
Okay, I fixed this in a .2 upload.
Debdiff against the .1 version in karmic-proposed attached for SRU
team's review.
I verified that avahi-daemon.conf actually lands in the eucalyptus-cc deb, and
gets installed to:
-rw-r--r-- root/root 620 2009-11-10 14:00
Accepted .2, please test once it's built.
--
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
Server Team, which is subscribed to
Accepted eucalyptus into karmic-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: eucalyptus (Ubuntu
** Branch linked: lp:ubuntu/karmic-proposed/avahi
--
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
Server Team, which is
** 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.
Good question for lucid. I don't know yet. I've got another proposal for
lucid that involves not shipping a specific configuration for avahi
daemon (the proposal is to use a txt record to publish the CC IP - the
same way as the type - cluster or node - is publish currently. That
would require some
Accepted avahi into karmic-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: avahi (Ubuntu Karmic)
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Fix Committed = In Progress
--
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
** 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.
Mathias - is the avahi change a hack for karmic only, or should be
proliferated to lucid? I. e. is this fix committed or wontfix for
lucid?
** Changed in: avahi (Ubuntu)
Status: New = Incomplete
** Changed in: avahi (Ubuntu)
Assignee: (unassigned) = Mathias Gug (mathiaz)
--
When
** Changed in: eucalyptus (Ubuntu Karmic)
Status: In Progress = Fix Committed
--
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
On Sat, Oct 31, 2009 at 12:40:46PM -, Martin Pitt wrote:
Mathias Gug [2009-10-30 21:52 -]:
-exec avahi-daemon -D
+script
+ opts=-D
+ [ -e /etc/eucalyptus/avahi-daemon.conf ] opts=${opts} -f
/etc/eucalyptus/avahi-daemon.conf
Upstart scripts are set -e by default,
On Mon, Nov 02, 2009 at 12:13:28PM -, Martin Pitt wrote:
Steve Langasek [2009-11-02 11:06 -]:
+ [ -e /etc/eucalyptus/avahi-daemon.conf ] opts=${opts} -f
/etc/eucalyptus/avahi-daemon.conf
Upstart scripts are set -e by default, so you are missing an ||
true here.
Mathias Gug [2009-10-30 21:52 -]:
-exec avahi-daemon -D
+script
+ opts=-D
+ [ -e /etc/eucalyptus/avahi-daemon.conf ] opts=${opts} -f
/etc/eucalyptus/avahi-daemon.conf
Upstart scripts are set -e by default, so you are missing an ||
true here. But even more, if
** Branch linked: lp:~mathiaz/ubuntu/karmic/avahi/k-eucalyptus-conf-
support
--
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
** Changed in: eucalyptus (Ubuntu)
Milestone: karmic-updates = None
--
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
** Branch linked: lp:~mathiaz/eucalyptus/k-eucalyptus-conf-support
--
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
Server
** Changed in: avahi (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Triaged = In Progress
** Changed in: eucalyptus (Ubuntu)
Assignee: Mathias Gug (mathiaz) = (unassigned)
--
When installing a node, euca_find_cluster fails to
Mathias, re: comment 15:
To fix this you need to manually publish the address (your upstart script)
*and* run avahi with publish-addresses=no. That way the right mapping address
is published and the new ones don't get auto-published.
--
When installing a node, euca_find_cluster fails to locate
Documented at
https://wiki.ubuntu.com/KarmicKoala/ReleaseNotes#UEC%20Node%20Controller%20installation%20failure%20in%20an%20existing%20UEC:
Extending an existing Ubuntu Enterprise Cloud may fail during node
controller installation started using the Install Ubuntu Enterprise
Cloud option on the
I tested the proposed update-based solution and it does *not* seem to
work:
* Added the avahi-publish upstart job
* Restart cluster
* Cluster has:
$ ip addr show eth0
2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qdisc pfifo_fast state UP
qlen 1000
link/ether 00:13:20:f8:4d:11 brd
Given that avahi-daemon ships with publish-addresses=yes, that may be
difficult to fix in a SRU.
--
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
How about this, for a h4ck1sh SRU:
- Change avahi's init script to prefer /etc/eucalyptus/avahi-daemon.conf if it
is present
- Change euca package to ship this.
This would avoid euca having to change another packages' conffile (which
is a grave policy violation for good reason), and should
Yes it would.
Other SRU-based options have been considered in #ubuntu-release by mdz,
mathiaz and kirkland, but were not mentioned here. That made me doubt
that the solution presented in comment 10 was appropriate. In light of
that discussion and Martin's solution, I think we can safely discuss
Shipping with publish-addresses=no won't fix the problem:
euca_find_cluster will not be able resolve the IP address of the CC at
all.
To confirm thierry's comment #11, I've tested the upstart job and it
failed. avahi-publish refuses to start since the CC IP is already
resolve to another name via
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
** 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.
** 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.
** Summary changed:
- 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
--
When installing a node, euca_find_cluster fails to locate the cluster
controller if instances
Another workaround is to explicitly publish the hostname/IP address
mapping on the CC:
avahi-publish -a $(hostname).local CC_IP
That way the avahi dns resolution will always resolve the hostname to
the correct IP address.
--
When installing a node, euca_find_cluster fails to locate the
Here is an upstart job that does the hostname/IP publication:
description Eucalyptus cluster controller IP publication
start on started eucalyptus-cc
stop on stopping eucalyptus-cc
script
. /etc/eucalyptus/eucalyptus.conf
. /etc/eucalyptus/eucalyptus-ipaddr.conf
exec
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Assignee: (unassigned) = Mathias Gug (mathiaz)
** Changed in: ubuntu-release-notes
Status: New = Triaged
** Changed in: ubuntu-release-notes
Importance: Undecided
46 matches
Mail list logo
