Not sure about logs from all Eucalyptus components. This problem seems
to be centered in the cluster controller code. I think the telling log
lines I've seen after the second euca-run-instances command are:
[Thu Apr 15 14:29:46 2010][001328][EUCAINFO ] RunInstances(): called
[Thu Apr 15
I wanted to add that we have since upgraded to 1.6.2-0ubuntu30.3 and
still witness this behavior regularly.
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
https://bugs.launchpad.net/bugs/564355
You received this bug
Public bug reported:
We are running eucalyptus 1.6.2-0ubuntu27 on lucid beta1 in MANAGED-
NOVLAN. I will retest as soon as is feasible with ubuntu30 but as I see
no mention of this issue/fix in the changelog I wanted to get the
information in your hands.
Eucalyptus has trouble allocating
I was able to repeat this behavior with ADDRSPERNET set to 128. The
system seems more prone to this behavior when a user makes requests for
large numbers of VMs in a security group and then attempts to add more.
Not sure if this bug manifests based on the size of requests or how many
IPs are
Public bug reported:
We are running eucalyptus 1.6.2-0ubuntu27 on lucid beta1. I will retest
this bug on the latest-and-greatest as soon as that is feasible on our
cluster.
We have been running many tests with the ROUNDROBIN scheduling policy.
As a test I changed it to GREEDY a little over a
Public bug reported:
When the function getSecretKey() in euca_conf tries to set SKEY and AKEY
it uses an unanchored regex with awk that can cause it to select the
credentials of any user with the word admin in their login name. I
imagine the intent was to select the 'admin' user but the way the
