lucid has seen the end of its life and is no longer receiving any
updates. Marking the lucid task for this ticket as Won't Fix.
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team,
I'm not able to reproduce it with 2.0.3. Aimon, if you still see this
issue, please open a new bug.
** No longer affects: eucalyptus/eucalyptus-devel
** Changed in: eucalyptus
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Hi Here is Log from CLC that corresponds to CC log you have seen above
(see attached). An interesting note about the attached log. There is
only one successful vm in the secgroup. All other fail with the attached
and above errors. When I create another secgroup, the new one behaves
normally and I
Forgot the log.
** Attachment added: clc-debug.log
https://bugs.launchpad.net/ubuntu/lucid/+source/eucalyptus/+bug/564355/+attachment/1715609/+files/clc-debug.log
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
We were not able to reproduce this on maverick / 2.0. Please set it back
to Triaged if anyone can.
** Changed in: eucalyptus (Ubuntu Maverick)
Status: Triaged = Invalid
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with
Marking Incomplete for the Lucid/Eucalyptus task -- we still need the
logs, as I and Dmitrri requested earlier on; marking triaged for the
Maverick/Eucalyptus task: I have been unable to reproduce it on
Maverick, but will keep on trying.
Note that this may well be a volume-related issue: I
** Tags added: server-mrs
--
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 notification because you are a member of Ubuntu
Server Team, which is subscribed
If someone has logs from all components they would be helpful, actually.
(Although it may *seem* like a CC problem, it *may* originate in the
CLC.) Also, if it is easy for someone to check if the problem has been
solved (as I suspect it has) in 2.0.0, currently in Maverick, that would
help a lot.
RC bugs need to be assigned to someone -- assigning to Carlos for
verification (or tracking Eucalyptus verification)
** Changed in: eucalyptus (Ubuntu Maverick)
Assignee: (unassigned) = C de-Avillez (hggdh2)
--
Second euca-run-instance request in same security group causes eucalyptus to
** Also affects: eucalyptus (Ubuntu Maverick)
Importance: High
Status: New
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
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
This also Effects 1.6.2 CentOS release. When ADDRPERNET is set to 256 it
causes same behavior with this error:
[Wed Aug 11 08:22:12 2010][005109][EUCADEBUG ] RunInstances(): params:
userId=admin, emiId=emi-54A01BEF, kernelId=eki-5A861EB7, ramdiskId=UNSET,
Actually this shows itself when at 64 or 128 also.
** Also affects: eucalyptus (CentOS)
Importance: Undecided
Status: New
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
** Changed in: eucalyptus (Ubuntu)
Milestone: lucid-updates = None
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: lucid-updates = None
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with security group
Won't have time to reproduce today or next week (away from cloud setup),
so i'll put it back in the pool for anyone to pick. Not pre-release
material anyway, potential SRU target.
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: Thierry Carrez (ttx) = (unassigned)
--
Second
Thierry says that he'll try to reproduce i.
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) = Thierry Carrez (ttx)
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: None = lucid-updates
--
Second euca-run-instance request in same security group causes
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: High
Status: New
** Changed in: eucalyptus (Ubuntu Lucid)
Assignee: (unassigned) = Dustin Kirkland (kirkland)
--
Second euca-run-instance request in same security group causes eucalyptus to
remove network assoicated with
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided = High
--
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 notification because you are a member of
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
20 matches
Mail list logo
