I first reproduced the problem on the training cloud, then installed the
PPA packages. The problem went away, the cloud is responsive within the
first two minutes of restarting the frontend.
--
eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart
** Also affects: eucalyptus (Ubuntu Karmic)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu Karmic)
Status: New = Triaged
** Changed in: eucalyptus (Ubuntu Karmic)
Importance: Undecided = High
** Changed in: eucalyptus (Ubuntu Karmic)
Assignee:
I have nominated this for Karmic, in the hopes of getting an SRU out
soon.
We think we have tracked this problem to a very simple fix...ensuring
that the iptables module gets loaded in initial eucalyptus upstart job.
I have uploaded eucalyptus_1.6~bzr931-0ubuntu7.5~ppa1 to the ubuntu-virt ppa:
Manually testing the change worked for me. I'll try the built package
shortly
--
eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart issues due to upstart networking behavior)
https://bugs.launchpad.net/bugs/503180
You received this bug
This bug was fixed in the package eucalyptus - 1.6.2~bzr1136-0ubuntu3
---
eucalyptus (1.6.2~bzr1136-0ubuntu3) lucid; urgency=low
* eucalyptus-cc.eucalyptus-cc-publication.upstart,
eucalyptus-common.eucalyptus.upstart, eucalyptus-network.upstart,
Okay, I talked to Scott about similar upstart situations last week, and
I think I have his blessing on what I thought would be hacky.
Basically, we need to create an additional, upstart (psuedo) job, that
would start on started networking, and basically loop until some
conditional is settled (in
** Summary changed:
- eucalyptus-cloud doesn't reply to requests (due to upstart networking issue)
+ eucalyptus-cloud doesn't reply to requests (eucalyptus doesn't work after
reboot or services restart issues due to upstart networking behavior)
--
eucalyptus-cloud doesn't reply to requests
It looks like starting eucalyptus on net-device-up IFACE=eth0 is not
sufficient. It definitely looks sensitive to startup order / network up
though. I'll let Dustin investigate this one deeper.
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this
Thank Thierry,
We've finally been able to (we believe) reproduce this type of condition
on our Lucid machines, and have figured out the reason why it is being
triggered on lucid UEC installations. The Eucalyptus front-end
components (cloud, walrus, sc) require that, on startup, the network
That makes sense. I will test with an upstart script that clearly waits
for eth0 up before starting eucalyptus and let you know.
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this bug notification because you are a member of Ubuntu
Server Team,
Greetings,
We're having trouble reproducing this problem on our lucid systems
against eucalyptus-cloud-1.6.2~bzr1124-0ubuntu3. We think that the
issue is possibly related to some process startup behavior, but it would
be great to get some more system information or a process by which the
issue
I hit it systematically on the following test:
Alpha2 ISO, UEC installer, select CLC+Walrus+CC+SC
Just after reboot (so, fresh boot, clearly), the right ports come up... but...
sudo euca_conf --get-credentials mycreds.zip stalls
sudo euca_conf --list-walruses answers You need to be on the CLC...
** Tags added: iso-testing
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
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
** Changed in: eucalyptus (Ubuntu)
Milestone: None = lucid-alpha-3
** Changed in: eucalyptus (Ubuntu)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: High
Assignee: Dustin Kirkland (kirkland)
Status: Confirmed
--
I've seen similar problems in the past, but waiting for some extended
time (15 minutes) solved it. In that time the Web UI was also not
working, the admin user was reported to not exist.
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this bug
I also have to kill -9 the remaining eucalyptus-cloud process after the
stop. I don't have the same exception in cloud-error.log. In cloud-
output.log everything seems normal, then nothing gets added anymore.
euca_conf is run, nothing shows in the log. Then after some time you
start getting tons
I ran into this one as well. I had to stop eucalyptus / start eucalyptus
to get a running system.
** Changed in: eucalyptus (Ubuntu)
Status: New = Confirmed
--
eucalyptus-cloud doesn't reply to requests
https://bugs.launchpad.net/bugs/503180
You received this bug notification because you
17 matches
Mail list logo
