Public bug reported:
This report is against the latest (as of now, 2011-11-27, 02:01 GMT-2)
Oneiric's x64 cloud image, available on http://cloud-
images.ubuntu.com/oneiric/current/ (which is Ubuntu 11.10 (Oneiric
Ocelot) Daily Build [2024]).
I tried to launch an instance on my Eucalyptus
As asked by SpamapS in #ubuntu-server, I quickly tested the current
Precise cloud image (Ubuntu 12.04 (Precise Pangolin) Daily Build
[2026]).
It didn't work.
I didn't analyze it, but comparing to what I've seen on Oneirice,
apparently the Kernel is ok (it manages to find /dev/sda1) and
Hello.
Just to inform that since yesterday after when I updated to the latest
version available on natty-proposed the servers are running good, and
have shown no symptoms of messages from the future being discarded
(verified through the absence of the error logs I was seeing in
Hello.
Just to inform that since yesterday after when I updated to the latest
version available on natty-proposed the servers are running good, and
have shown no symptoms of messages from the future being discarded
(verified through the absence of the error logs I was seeing in
Hello.
I've just installed the update from natty-proposed on my 3 servers (2
NCs, 1 CC), and they seem to be fine. I will confirm if everything is
still OK tomorrow, since the errors were intermittent.
It is the first time I use -proposed, so I have a question: if
everything goes smooth, and you
Hello.
I've just installed the update from natty-proposed on my 3 servers (2
NCs, 1 CC), and they seem to be fine. I will confirm if everything is
still OK tomorrow, since the errors were intermittent.
It is the first time I use -proposed, so I have a question: if
everything goes smooth, and you
Public bug reported:
In both EucalyptusNC/services.xml and EucalyptusCC/services.xml there's
no ClockSkewBuffer (nor TimeToLive nor PrecisionInMilliseconds),
therefore messages from the future (from the webservice's point of
view) won't be accepted, even if the difference in time is minimal.
Public bug reported:
In both EucalyptusNC/services.xml and EucalyptusCC/services.xml there's
no ClockSkewBuffer (nor TimeToLive nor PrecisionInMilliseconds),
therefore messages from the future (from the webservice's point of
view) won't be accepted, even if the difference in time is minimal.
