OK. I think I've figured out what is causing this.
in 100% of the failed instances that I'm seeing today, the instance has its
public ip identical to its private ip.
Ie, the following is euca-describe-instances output of a failed instance:
INSTANCEi-2F1A0573 emi-E58B1525172.19.1
I'm attaching iptables-save output on CLC, CC, NC1 and NC2. I really
don't think its of that much value due to the previous comment, but it
was requested.
** Attachment added: "iptables-save output on CLC, CC, NC1, NC2 in failing
state"
http://launchpadlibrarian.net/48821877/failing-iptables
I verified general functionality of the changes with:
$ dd if=/dev/zero of=out count=1 bs=1M
$ ec2-bundle-image --image out --cert ~/ec2/cert.pem --privatekey ~/ec2/pk.pem
--user 950047163771 --arch i386
$ ec2-upload-bundle --access-key ${access_key} --secret-key ${secret_key} \
--bucket ${
** Also affects: ec2-ami-tools (Ubuntu Karmic)
Importance: Undecided
Status: New
** Also affects: ec2-ami-tools (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: ec2-ami-tools (Ubuntu Karmic)
Status: New => Triaged
** Changed in: ec2-ami-tools (Ubuntu Luc
I'm attaching 2 files. failed-instance-cc.log (i-3812076B) and good-
instance-cc.log (i-42A70769)
Unfortunately, I dont think they'll be of a whole lot of use, as the
'AssignAddress' calls are not tied to the instance id in the log, so I
dont know how to tell which call was for which instance id.
** Attachment added: "cc.log during successful run of i-42A70769"
http://launchpadlibrarian.net/48830292/good-instance-cc.log.bz2
--
metadata service returns empty data with 200 OK
https://bugs.launchpad.net/bugs/566792
You received this bug notification because you are a member of Ubuntu
Bug
On Thu, 20 May 2010, Etienne Goyer wrote:
> > (MANAGED modes). In order for the meta-data service to work, the VM
> > needs to be assigned a public IP, and it looks like this operation is
> > failing (indicated by the fact that the public/private IPs being
> > reported are both from the private I
> 'filesystem' is documented as being appropriate for most normal
> services, so surely many other services have the same problem? Most
> notably, rc-sysinit starts on filesystem, so you'll never reach runlevel
> 2 if that event is never emitted. It seems to me that any change I
> might make in s
hm... now that i'm reading the man page you directed me at, the
nobootwait and optional flags do seem to solve this issue.
at very least, though, there is an educational problem here. I was
unaware of these options as I'm sure several sysadmins or users are.
--
ssh server doesn't start when ir
Public bug reported:
Binary package hint: udev
On lucid, I've added the following rule in /etc/udev/rules.d/85-foo.rules:
ACTION=="add", RUN+="/tmp/foo"
then, /tmp/foo has:
#!/bin/sh
udevadm info --export-db > ${0}.stdout 2>${0}.stderr
if I run udevd with '--debug --debug-trace', then /tmp/foo.
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/49971649/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/49971650/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49971651/Dependencies.txt
** A
testing shows that '--debug-trace' has no effect, its the '--debug' flag
itself.
--
udevd daemon run with --debug affects output of 'udevadm info'
https://bugs.launchpad.net/bugs/591460
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Attachment added: "entire output of foo.stderr"
http://launchpadlibrarian.net/49972534/foo.stderr
--
udevd daemon run with --debug affects output of 'udevadm info'
https://bugs.launchpad.net/bugs/591460
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
I'm playing with eucalyptus, and attaching and detaching a block device as a
virtio (bug 588410)
$ euca-attach-volume --instance ${inst} --device /dev/vdc ${vol}
VOLUME vol-5EC30651
Then,
$ euca-detach-volume ${vol}
The device names start as /dev/vda and go through to /d
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/49973588/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/49973589/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49973590/Dependencies.txt
** A
The bug is about the official package being reported as "not genuine".
If a user has installed off of official media, removed the cache files
(or changed their mirror) they are then told that the bug they found is
in a package that is "not a genuine Ubuntu package". Its at very least
confusing, wor
The explicit point of the message is tell the user that PPA packages or
other 3rd party software packages cannot be reported by apport. I do
not think that that is a bug at all, but only in identifying something
that *is* a genuine package as *not* a genuine package.
--
Without an apt cache, pac
I do not really have the time to test the upstream kernel. However,
looking at the source of drivers/block/virtio_blk.c , I would guess that
this bug does exist upstream. My (possibly to quick) read of
virtblk_probe and virtblk_remove seem to me to be indicating the static
variable "index" and ne
2 things.
a.) i just realized that the simple 'index--' wouldn't suffice as that would
result in:
- add vda
- add vdb
- add vdc
- remove vdb
- add vdc !!
b.) i did reproduce with the upstream build linux-image-2.6.34-020634-generic .
--
virtio block devices names are not recycled
https://bugs.la
I added cloud-utils as I think that this really should be there rather
than in cloud-init.
** Also affects: cloud-utils (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-utils (Ubuntu)
Status: New => Triaged
--
update/replace ec2-get-info with ec2metadata
https://
** Changed in: cloud-init (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: cloud-utils (Ubuntu)
Status: Triaged => Fix Committed
--
update/replace ec2-get-info with ec2metadata
https://bugs.launchpad.net/bugs/547019
You received this bug notification because you are a membe
@David,
Why are you setting the 'patch-forwarded-upstream' tag on this bug, the patch
has *not* been forwarded upstream. in fact, there is no patch or solution for
the bug.
--
metadata service returns empty data with 200 OK
https://bugs.launchpad.net/bugs/566792
You received this bug notific
I've verified this with:
$ ec2-run-instances ami-2d4aa444
$ ssh host
% echo deb http://archive.ubuntu.com/ubuntu/ lucid-proposed restricted main
multiverse universe |
sudo tee /etc/apt/sources.list.d/lucid-proposed.list
% sudo apt-get update
% sudo apt-get install cloud-init
% sudo rm -f /var
** Tags added: verification-done
** Tags removed: verification-needed
--
uec images should wait longer for metadata service
https://bugs.launchpad.net/bugs/571271
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
** Tags removed: patch-forwarded-upstream
--
metadata service returns empty data with 200 OK
https://bugs.launchpad.net/bugs/566792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
** Bug watch added: Debian Bug tracker #522739
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522739
** Also affects: mtx (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522739
Importance: Unknown
Status: Unknown
--
tab completion does not work
https://bugs.launch
My feeling is that this is likely much more related to Xorg than it is
to samba.
Removing samba from the picture, are you able to log out of your session
and log back in ?
** Also affects: xorg-server (Ubuntu)
Importance: Undecided
Status: New
** Changed in: samba (Ubuntu)
Importanc
** Package changed: samba (Ubuntu) => system-config-printer (Ubuntu)
--
Segfault when trying to add a Windows printer via SAMBA
https://bugs.launchpad.net/bugs/367473
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => High
** Changed in: eucalyptus (Ubuntu)
Status: New => Triaged
--
Problems with node registration
https://bugs.launchpad.net/bugs/585108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Changed in: openssh (Ubuntu)
Status: New => Triaged
** Changed in: openssh (Ubuntu)
Importance: Undecided => Medium
--
ssh server doesn't start when irrelevant filesystems are not available
https://bugs.launchpad.net/bugs/583542
You received this bug notification because you are a m
** Changed in: php5 (Ubuntu)
Status: New => Triaged
** Changed in: php5 (Ubuntu)
Importance: Undecided => Medium
--
php5 crashed with SIGSEGV in execute()
https://bugs.launchpad.net/bugs/577710
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: dbconfig-common (Ubuntu)
Status: New => Triaged
** Changed in: dbconfig-common (Ubuntu)
Importance: Undecided => Low
--
package phpmyadmin 4:3.3.2-1 failed to install/upgrade: subprocess installed
pre-removal script returned error exit status 1
https://bugs.launchpad.ne
are you able to test if this issue is present in maverick , which has
1:5.5p1-4ubuntu1 ?
Additionally, in the interim, you can quite likely use Collin's ppa for
lucid:
http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/ubuntu/2010-05-10-openssh-5.5p1
-for-lucid.html
** Changed in: openssh
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => Medium
--
Instance losses associated address
https://bugs.launchpad.net/bugs/585784
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
Does 09:28:25 correlate with the time of reboot ?
How quickly does the reboot occur?
Also, could you please run 'apport-collect 585002', which will attach
debugging information to this bug.
** Changed in: qemu-kvm (Ubuntu)
Status: New => Incomplete
--
Qemu/KVM Ubuntu 10.04 guest reboots
Maverick has 1.3.12-3ubuntu1 , the bug was fixed in debian 1.3.12-2.
As such, I'm marking this fix-released. Please re-open if you test maverick
and find the bug still present.
** Changed in: mtx (Ubuntu)
Status: New => Fix Released
--
tab completion does not work
https://bugs.launchpa
>From the DpkgTerminalLog, the 'stop' script failed to run for mysql. From the
>content above (apparently in kern.log ?) there may have been no
>/etc/mysql/my.cnf . (user removal?)
--
package mysql-server-5.1 5.1.37-1ubuntu5 failed to install/upgrade: subprocess
new pre-removal script return
** Also affects: eucalyptus (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: None => lucid-updates
--
Problems with node registration
https://bugs.launchpad.net/bugs/585108
You received this bug notification because you are a memb
** Changed in: eucalyptus (Ubuntu Lucid)
Milestone: None => lucid-updates
--
metadata service returns empty data with 200 OK
https://bugs.launchpad.net/bugs/566792
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I think you will need to add execute permission to your $HOME directory
for other, so that apache can read it, and make sure that public_html
has other readabilithy also.
Can you please try that?
** Changed in: apache2 (Ubuntu)
Status: New => Incomplete
--
Apache2 userdir does not like e
** Changed in: logwatch (Ubuntu)
Status: New => Triaged
** Changed in: logwatch (Ubuntu)
Importance: Undecided => Medium
--
missing named filter/service patterns
https://bugs.launchpad.net/bugs/584229
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: qemu-kvm (Ubuntu)
Importance: Undecided => Low
** Changed in: qemu-kvm (Ubuntu)
Status: New => Triaged
--
qemu-img convert crashes converting vmdk
https://bugs.launchpad.net/bugs/584368
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Fix Committed => Fix Released
--
[SRU] euca-get-console-output gives first 64k of output, not most recent
https://bugs.launchpad.net/bugs/566793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: eucalyptus (Ubuntu Lucid)
Status: Fix Released => Fix Committed
--
[SRU] euca-get-console-output gives first 64k of output, not most recent
https://bugs.launchpad.net/bugs/566793
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'm marking this as 'Invalid' . It really is "working as designed".
when you select Encrypted home, you're also selecting it to be private.
The assumption is that if you are concerned about the readability of
your data when the system is off, you would rather not have other users
read the data whi
I verified the initial test case (with user data while loop on)
$ dpkg-query --show eucalyptus*
eucalyptus-cc 1.6.2-0ubuntu30.1
eucalyptus-cloud1.6.2-0ubuntu30.1
eucalyptus-common 1.6.2-0ubuntu30.1
eucalyptus-gl 1.6.2-0ubuntu30.1
eucalyptus-java-common 1.6.2-0ubuntu30.1
eucalyptu
I think i have to take back my "it worked" statement. the first 'get-
console-output' worked fine.
The second has been running for 6 minutes, 30 seconds and has printed out the
following:
-
4 0 8
path=/services/Eucalyptus/?AWSAccessKeyId=WKy3rMzOWPouVOxK1p3Ar1C2u
Something is definitely broken.
After the above eventually returned (17 minutes, a failed command and more
timeouts like above on the screen), I restarted eucalyptus and tried again
$ sudo restart eucalyptus
# wait
$ sh -c 'date; time euca-get-console-output i-431B08E0; date' 2>&1 | tee
out.first
Public bug reported:
When trying to verify that bug 566793 was fixed, I ran an instance, did
- euca-get-console-output i-431B08E0
- euca-get-console-output i-431B08E0 (this one times out as you can see in that
bug)
- sudo restart eucalyptus
- euca-run-instances emi-BF971F9B
Then, a euca-describe
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/49268839/Dependencies.txt
** Attachment added: "EucalyptusAxis2cLog.gz"
http://launchpadlibrarian.net/49268840/EucalyptusAxis2cLog.gz
** Attachment added: "EucalyptusCCLog.gz"
http://launchpadlibrarian.net/49268841/Eu
Is this easily reproducible for you ? always reproducible ?
It seems that you might be hitting the same bug 566792 .
The symptom of the request to the metadata service coming from the CC is
the same.
--
Instance without public ip fails reading metadata with separate CC & CLC
https://bugs.launchp
On Fri, 28 May 2010, Mike Cook wrote:
> > I happen to [know] from experience that it does work for addressing
> > private. My guess is that Eucalyptus especially takes care of the case
> > where '--addressing private' was used.
>
> Scott, were the CC & CLC the same host when it worked for you? I d
I've verified, this is fairly reproducible:
$ euca-run-instances emi-F3281995
$ sudo eucalyptus restart
# wait
$ euca-run-instances emi-F3281995
Now I have 2 instances with same private and public IPs.
--
2 instances with same public and private IP
https://bugs.launchpad.net/bugs/586903
You re
this is easily reproducible on lucid in ec2.
--
libvirtd will not run on virtual machine
https://bugs.launchpad.net/bugs/556326
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
htt
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
Problems with node registration
https://bugs.launchpad.net/bugs/585108
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
vmbuilder that is used for building UEC images is (right now)
http://bazaar.launchpad.net/~ubuntu-virt/vmbuilder/0.11/
That should have all the code you need to build.
our automated builds (https://code.launchpad.net/~ubuntu-on-
ec2/vmbuilder/automated-ec2-builds) build from that branch out of a
** Description changed:
Using ubuntu 10.04, i have eucalyptus-nc running in the node controller
but does not have nc.log. In the cc, if i run euca_conf --discover-nodes
it find no nodes. Even if i run euca_conf --register-nodes NODE_IP, i
receive a success message (done), but no nodes are
Dustin and Daniel worked on this a bit more on friday and seem to have
at least found a workaround. The database was getting stuck. Per
Dustin, it at least appears that this is not a uec-
publish-[image,tarball] as I had thought it might be.
--
instance stays in pending for > 1 hour, then to te
** Changed in: mountall (Ubuntu)
Milestone: None => ubuntu-10.04-beta-1
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Just for a small update, I've been trying to back upstart to the older
version and see if I can't reproduce there, but have not been able to
due to bug 532682.
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification bec
I'm not sure why I'm so lucky, but I hit this more times than not...I'm
almost completely unable to register an image that will boot.
It seems critical to me, as it blocks all usage of the installed UEC.
--
instance stays in pending for > 1 hour, then to terminated
https://bugs.launchpad.net/bug
I took the upstart image that was failing (20100303) and replaced the
upstart 0.6.5-4 with 0.6.5-3.
I've yet to make the instance fail (admittedly only 5 tests, but with
0.6.5-4, success was quite rare).
** Package changed: mountall (Ubuntu Lucid) => upstart (Ubuntu Lucid)
--
cloud-init job not
The kernel listed above is now available in "ubuntu-kernels-testing"
buckets. In the next week or two we hope to have fully released
versions of images with these kernels. Thanks John!
--
ec2 kernel needs CONFIG_BLK_DEV_LOOP=y and other config changes
https://bugs.launchpad.net/bugs/428692
You
On Wed, 3 Mar 2010, william_lin wrote:
> I'm using Eucalyptus 1.6
> It seems like bundling from a running instance always generates an image that
> cannot be used(ssh doesn't work). Both euca2ools 1.0 & 1.2 do not work. Here
> are my steps:(using euca2ools 1.2)
> 1. launch an instance based on a
Public bug reported:
Binary package hint: cloud-init
cloud-init provides a replacement for ec2-init. However, on an upgrade
from ec2-init, the "first boot init" that cloud-init runs wil run even
though ec2-init has already done so.
On upgrade from ec2-init, cloud-init should recognize the situa
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40064923/Dependencies.txt
--
on upgrade from ec2-init, cloud-init will re-run
https://bugs.launchpad.net/bugs/531378
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ium
** Changed in: cloud-init (Ubuntu)
Status: New => Triaged
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
on upgrade from ec2-init, cloud-init will re-run
https://bugs.launchpad.net/bugs/531378
You received this bug notification because yo
Public bug reported:
Binary package hint: euca2ools
euca-describe-instances appends a space to the instance state in its output.
The output should be straight tab delimited output.
This makes something the following fail:
awk '-F\t' '$6 = "running" && { print $0 }'
Additionally the code is f
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40092263/Dependencies.txt
** Also affects: eucalyptus
Importance: Undecided
Status: New
--
euca-describe-instances shows state "running ", not "running"
https://bugs.launchpad.net/bugs/531453
You received this bu
** Branch unlinked: lp:~smoser/eucalyptus/euca2ools-1.0.fixes
--
euca-describe-instances shows state "running ", not "running"
https://bugs.launchpad.net/bugs/531453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Proposed fix is at
http://bazaar.launchpad.net/~smoser/eucalyptus/euca2ools-1.0.bug531453/revision/266
.
--
euca-describe-instances shows state "running ", not "running"
https://bugs.launchpad.net/bugs/531453
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
Just noticed that this fix also fixes a bug in euca-run-instances that
outputs 'None' for a instance that has no ramdisk rather than an empty
string:
$ euca-run-instances --instance-type c1.medium --key mykey emi-4CD51A12
RESERVATION r-4F2E087C admin admin-default
INSTANCEi-4BCD
Public bug reported:
Binary package hint: upstart
Somewhere between uec image build 20100224 (beta1) and 2010228, the
cloud-init job stopped running.
cloud-init job has:
start on (mounted MOUNTPOINT=/ and net-device-up IFACE=eth0)
I'll attach the complete diff between the 2 manifests (it is a
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40094448/Dependencies.txt
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "diff of manifests 20100224 -> 20100228"
http://launchpadlibrarian.net/40094554/20100224-to-20100228.diff
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubun
** Attachment added: "successful boot serial console with debug"
http://launchpadlibrarian.net/40094574/console-successful-debug.txt
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member o
** Attachment added: "failed boot serial console with debug"
http://launchpadlibrarian.net/40094568/console-fail-debug.txt
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
B
I did reproduce failure with debug enabled, and attached a log of the
same image successful and fail above.
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Re-attaching succesful boot log, previous one had 2 boots in it. This
has only the first.
** Attachment removed: "successful boot serial console with debug"
http://launchpadlibrarian.net/40094574/console-successful-debug.txt
** Attachment added: "successful boot serial console with debug"
** Changed in: upstart (Ubuntu)
Importance: Undecided => Critical
--
cloud-init job not running in eucalyptus without ramdisk
https://bugs.launchpad.net/bugs/531494
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
The images have 2G filesystem. the default 'small' is "2G disk".
However, swap has to be accounted for. So, if you launch an image with
2G filesystem in a instance size with 2G disk, it will fail as Borris
explained above.
I *think* that in karmic, somehow our 2G filesystems magically fit into
Public bug reported:
euca-get-console-output seems to repeat itself once for every time it is run,
and get slower also.
For example:
$ id=i-42DC08AD;
$ euca-describe-images emi-A89717DA
IMAGE emi-A89717DA
lucid-server-20100224/lucid-server-uec-amd64.img.manifest.xml admin
available
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/40096641/Dependencies.txt
--
euca-get-console-output repeats output on subsequent runs
https://bugs.launchpad.net/bugs/531536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
** Also affects: eucalyptus
Importance: Undecided
Status: New
** Changed in: eucalyptus (Ubuntu)
Importance: Undecided => High
--
euca-get-console-output repeats output on subsequent runs
https://bugs.launchpad.net/bugs/531536
You received this bug notification because you are a mem
** Changed in: euca2ools (Ubuntu Lucid)
Importance: Undecided => Medium
--
euca-describe-instances shows state "running ", not "running"
https://bugs.launchpad.net/bugs/531453
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => In Progress
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
cloud-init cloud-config-mounts can add duplicate fstab entries
https://bugs.launchpad.net/bugs/524562
You received th
I'm marking this as critical. This is serious error in functionality
that makes the console almost completely unusable.
** Changed in: eucalyptus (Ubuntu Lucid)
Importance: Medium => Critical
--
euca-get-console-output repeats output on subsequent runs
https://bugs.launchpad.net/bugs/531536
I've tested this on karmic released uec image (20100121):
$ hostname
172
$ echo deb http://archive.ubuntu.com/ubuntu/ karmic-proposed restricted main
multiverse universe | sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt-get update
$ apt-cache policy ec2-init
ec2-init:
Installed: 0.4.9
I've tested this on karmic released uec image (20100121):
$ sudo apt-get update && sudo apt-get install python2.4
$ echo deb http://archive.ubuntu.com/ubuntu/ karmic-proposed restricted main
multiverse universe | sudo tee /etc/apt/sources.list.d/proposed.list
$ sudo apt-get update
$ apt-cache pol
Public bug reported:
On a fresh install of lucid eucalyptus, I did the following:
A. download lucid 20100303 (http://uec-images.ubuntu.com/lucid/)
B. publish it
uec-publish-tarball lucid-server-uec-amd64.tar.gz lucid-20100303
C. extract
tar -Sxvzf lucid-server-uec-amd64.tar.gz
D. mount ima
I'm attaching steps that I did after the lucid-image steps above with a
karmic image.
Note, that the karmic image has a ramdisk. This didn't seem to change
anything, the karmic image fails to boot also.
** Attachment added: "karmic steps, showing same issue (done after lucid above)"
http://la
** Description changed:
On a fresh install of lucid eucalyptus, I did the following:
A. download lucid 20100303 (http://uec-images.ubuntu.com/lucid/)
B. publish it
-uec-publish-tarball lucid-server-uec-amd64.tar.gz lucid-20100303
+ uec-publish-tarball lucid-server-uec-amd64.tar.gz
I followed the attachd file (karmic steps...) on a fresh install of
Eucalyptus and it recreates the problem. That seems to me to rule out
the "ramdiskless" scapegoat.
$ euca-describe-images
IMAGE eki-68691AF0
karmic-20100127/karmic-server-uec-amd64-vmlinuz-virtual.manifest.xmladmin
$ dpkg-query --show openjdk-6-jre-headless
openjdk-6-jre-headless 6b18~pre3-0ubuntu1
$ unset EC2_JVM_ARGS
$ ec2-describe-images --private-key pk.pem --cert cert.pem ami-a108e7c8
IMAGE ami-a108e7c8
099720109477/ebs/ubuntu-images-milestone/ubuntu-lucid-10.04-beta1-amd64-server-20100317
099720
Verified that ubuntu-bug works in
$ dpkg-query --show eucalyptus-common
eucalyptus-common 1.6.2-0ubuntu20
--
Eucalyptus apport fails: AttributeError: __AptDpkgPackageInfo instance has no
attribute 'get_versions'
https://bugs.launchpad.net/bugs/520775
You received this bug notification bec
I'm moving this to 'Importance' medium, but might want it to be 'high'.
This is the code path that Eucalyptus uses for EBS. EBS is suposed to
be reliable storage for cloud instances. With that dmesg output you
don't get warm fuzzy feelings about how reliable your data is.
** Changed in: linux (
** Patch added: "patch to compress log files before attaching"
http://launchpadlibrarian.net/41759121/bug541486-eucalyptus-compress-logs.diff
--
ubuntu-bug eucalyptus-common attaches massive files
https://bugs.launchpad.net/bugs/541486
You received this bug notification because you are a mem
** Patch added: "add compress arg to attach_file in apport hookutils"
http://launchpadlibrarian.net/41759197/bug541486-apport-add-compress.diff
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
ubuntu-bug eucalyptus-common attaches massive files
https://bugs.lau
I added an apport task, as I'd like to have this fixed by adding support
for compression of files into hookutils of apport, and then use that in
eucalyptus's hook.
See the attached 2 patches for my solution.
--
ubuntu-bug eucalyptus-common attaches massive files
https://bugs.launchpad.net/bugs/5
I think at the moment we'll just want to attach the entire log. At some
point the log files will hopefully be more reasonably sized by turning
down debug output or such. Compression will turn 60M or so down into <
10, which isn't *too* bad.
Thanks for the report['FooFile'] syntax.
--
ubuntu-bu
601 - 700 of 8709 matches
Mail list logo
