Marking Invalid, as the comments suggest it's actually a bug in the
deployment environment and not one that should be encountered in the
wild.
** Changed in: eucalyptus (Ubuntu)
Status: Triaged = Invalid
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
** Changed in: eucalyptus (Ubuntu)
Status: Confirmed = Triaged
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
So euca_find_component could be fixed to be able to use #2 types,
however I'm unsure we should support the case of multiple CCs with the
same cluster name running in the same network. That opens the door for
lots of bugs, I think. From which CC would the NC download its preseed ?
At least the
Yeah, I agree with your last comment.
A cluster with that name already exists on this network. Pick another.
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received this bug notification because you are a member of
Marking confirmed, as I hit this on the test rig on all of my nodes
against Alpha3 ISOs.
** Changed in: eucalyptus (Ubuntu)
Status: Incomplete = Confirmed
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received
@Dustin: see my comment 4 above: I think this bug is linked to the
reinstall of CCs under the same cluster name (avahi will call it #2 only
if there is another one already published under that name), so it might
be an artifact of the test environment.
To workaround it, make sure nothing is
Okay, I found a suitable workaround, at least, for the lab testing ...
Simply ensure that all systems are powered off before starting a new
run.
I suspect the reason I hit this was because I had deployed a topo2 setup
(with a standalone CC). Then I setup a topo1 installation, which has a
** Changed in: eucalyptus (Ubuntu)
Importance: High = Medium
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Sounds like something has been advertising itself as UEC-TEST1 and
your CC advertised itself under the same name and got published as UEC-
TEST1 #2. That confused the logic in Colin's get_component which failed
to parse the IP from the announcement.
So there may be a bug in that last part, but I
On the CC:
ubu...@cempedak:~$ ps -ef | grep avahi
avahi 991 1 0 18:07 ?00:00:00 avahi-daemon: running
[cempedak.local]
avahi 992 991 0 18:07 ?00:00:00 avahi-daemon: chroot helper
root 1411 1 0 18:08 ?00:00:00 avahi-publish -s Walrus
This is with eucalyptus 1.6.2-0ubuntu1.
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to eucalyptus in ubuntu.
--
Installing directly from the archive using the netboot installer works
correctly with 1.6.2-0ubuntu2.
--
UEC NC failed to fetch preseed.conf from CC using lucid-server-amd64-20100218
https://bugs.launchpad.net/bugs/524147
You received this bug notification because you are a member of Ubuntu
12 matches
Mail list logo
