** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: ubuntu-on-ec2
Status: Triaged => Invalid
--
Provide Ubuntu EC2 kernels with 1000Hz timer (for VOIP/Asterisk)
https://bugs.launchpad.net/b
** Tags added: ec2-images uec-images
--
Wait for network before downloading ssh credentials or user-data
https://bugs.launchpad.net/bugs/308530
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
** Tags added: ec2-images uec-images
** Changed in: ubuntu-on-ec2/hardy
Status: Confirmed => Invalid
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
--
landscape-client cron job is broken
https://bugs.launchpad.net/bugs/421707
You received this bug
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
Update Hardy kernel AKI for local privilege escalation
https://bugs.launchpad.net/bugs/420635
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Changed in: landscape-client (Ubuntu)
Status: New => Triaged
** Changed in: landscape-client (Ubuntu Hardy)
Status: New => Triaged
** Changed in: landscape-client (Ubuntu)
Importance: Undecided => Medium
** Changed in: landscape-client (Ubuntu Intrepid)
Status: New =>
for this task 'linux (Ubuntu)' this bug will be closed when we get
karmic kernel (bug 418130).
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu Hardy)
Status: New => Triaged
** Change
** Changed in: ubuntu-on-ec2/hardy
Assignee: Scott Moser (smoser) => (unassigned)
** Changed in: landscape-client (Ubuntu Hardy)
Assignee: (unassigned) => Scott Moser (smoser)
--
landscape-client cron job is broken
https://bugs.launchpad.net/bugs/421707
You received th
** Changed in: ubuntu-on-ec2/hardy
Importance: High => Undecided
** Changed in: ubuntu-on-ec2/hardy
Status: Triaged => Invalid
** Changed in: ubuntu-on-ec2/hardy
Assignee: Scott Moser (smoser) => (unassigned)
** Changed in: ubuntu-on-ec2
Status: Fix Released =
** Changed in: ubuntu-on-ec2/hardy
Importance: Medium => Undecided
--
landscape-client cron job is broken
https://bugs.launchpad.net/bugs/421707
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
> Is there any reason this couldn't land in Ubuntu proper (throug the SRU
> process)?
I've verified that this bug is present in released images of both hardy
and intrepid. On the intrepid image, i did an
apt-get install launchpad-client
there were no updates available.
I think we really need t
On Thu, 10 Sep 2009, Steve Langasek wrote:
> what other changes are needed on the eucalyptus package for this?
bug 426438 ( https://bugs.launchpad.net/vmbuilder/+bug/426438 )
--
When running Ubuntu as an Eucalyptus VM instance, module acpiphp is not
available to be loaded, complicating the use
> what other changes are needed on the eucalyptus package for this?
Sorry for the incomplete thought. I was trying to say that
a.) we need to document how to get acpiphp in ramdisk if the user makes
their own. https://help.ubuntu.com/community/Eucalyptus mentions how to
do this (add it to /etc/
> mount: could not find any free loop device
> ERROR: execution failed: "mount -o loop /mnt/fed11-irc-kernel2.6.31
> /mnt/img-mnt"
Dylan,
Could you please try installing the appropriate (i386 or x86_64)
linux-image deb in the instance. At
https://edge.launchpad.net/~timg-tpi/+archive/ppa use:
This is fixed in latest ec2-init packages. I have verfied functional
user-data scripts in alpha5 release.
** Changed in: ec2-init (Ubuntu Jaunty)
Assignee: Scott Moser (smoser) => (unassigned)
** Changed in: ec2-init (Ubuntu Karmic)
Status: Triaged => Fix Released
** Chan
** Changed in: ec2-init (Ubuntu Hardy)
Importance: Undecided => Critical
** Changed in: ec2-init (Ubuntu Intrepid)
Importance: Undecided => Medium
--
Wait for network before downloading ssh credentials or user-data
https://bugs.launchpad.net/bugs/308530
You received this bug notification b
I'm looking at the ubuntu-on-ec2 ppa at https://launchpad.net/~ubuntu-
on-ec2/+archive/ppa , specifically both https://launchpad.net/%7Eubuntu-
on-ec2/+archive/ppa/+sourcepub/667702/+listing-archive-extra (hardy) and
https://launchpad.net/%7Eubuntu-on-ec2/+archive/ppa/+sourcepub/667837
/+listing-ar
** Tags added: ec2-images
--
Main Inclusion Request: linux-ec2
https://bugs.launchpad.net/bugs/427658
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
https://lists.ubuntu.com/mail
** Tags added: ec2-images
--
Karmic i386 EC2 kernel emulating unsupported memory accesses
https://bugs.launchpad.net/bugs/427288
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
ht
>From Eric Hammond:
| I ended up with the following code when I build images for EC2;
| not sure if it fixes the bug just mentioned:
| http://paste.ubuntu.com/268982/
|> chroot $imagedir apt-get install -y libc6-xen
|> echo 'hwcap 0 nosegneg' > $imagedir/etc/ld.so.conf.d/libc6-xen.conf
|>
The next thing to be done here is to test if this bug is fixed with
libc6-xen (http://packages.ubuntu.com/karmic/libc6-xen).
I will test that.
libc6-xen depends on libc6 and says "will be selected instead when
running under Xen. " . Hopefully that means no negative affect if this
package is inst
just for the record, John opened bug 427288 to address the boot warning
in comment 22.
--
Karmic EC2 images don't use a karmic kernel
https://bugs.launchpad.net/bugs/418130
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I did a quick test to see if simple installation of libc6-xen would solve
this issue. It appears not. See below for details:
[localsys]$ ec2-run-instances --user-data foo \
--kernel aki-9c04e4f5 --ramdisk ari-9e04e4f7 ami-3520c05c
# note '--user-data foo' is just to work around bug 419306
[l
some more information
on the same system described above, doing additional things removes the
warning:
$ echo 'hwcap 0 nosegneg' | sudo tee -a /etc/ld.so.conf.d/libc6-xen.conf
$ sudo ldconfig
$ sudo apt-get --purge remove libc6-i686
Eric pointed at
-
http://groups.google.com/group/ec2ubuntu/b
I've verified that this is fixed in the nightly build from 20090910,
which is now uploaded and registerd as ami-a40fefcd (i386) or ami-
a20fefcb (x86_64).
The instance is reachable on boot with or without passing --user-data.
--
boto.utils.get_instance_userdata() hangs for a long time if no user
quire parsing the index.html.
** Affects: vm-builder (Ubuntu)
Importance: Low
Assignee: Scott Moser (smoser)
Status: Confirmed
** Tags: uec-images
--
rename uec kernel/ramdisk for automated downloading or easier doc
https://bugs.launchpad.net/bugs/444598
You received thi
This is really towards the publishing scripts, but marking package as
vm-builder.
** Package changed: ubuntu => vm-builder (Ubuntu)
--
rename uec kernel/ramdisk for automated downloading or easier doc
https://bugs.launchpad.net/bugs/444598
You received this bug notification because you are a mem
or
simply documentation.
** Affects: vm-builder (Ubuntu)
Importance: Medium
Assignee: Scott Moser (smoser)
Status: New
** Tags: uec-images
** Changed in: vm-builder (Ubuntu)
Importance: Undecided => Medium
** Changed in: vm-builder (Ubuntu)
Assignee: (unassig
Per John (#ubuntu-server)
10/02/09 19:15:06 anyway, here they are aki=aki-c6896aaf,
ari=ari-d8896ab1
10/02/09 19:15:44 i386: aki-e2896a8b ari-e4896a8d
10/02/09 19:16:14 there are also, almost identical kernels with
Hz=250 and kexec
10/02/09 19:16:48 x86_64: aki-5e896a37 ari-50896a39
10/02/0
Could the opener of this bug (or interested parties) please test beta
kernels:
US 32-bit ami-52be5d3b
US 64-bit ami-5ebe5d37
Europe 32-bit ami-544c6720
Europe 64-bit ami-564c6722
Also, as per John,
10/02/09 19:16:14 there are also, almost identical kernels with
Hz=250 and kexec
10/02/09 19:16:
*** This bug is a duplicate of bug 440757 ***
https://bugs.launchpad.net/bugs/440757
** This bug has been marked a duplicate of bug 440757
ec2-images have ubuntu.canonical.com in /etc/hosts
--
ec2-images have ubuntu.canonical.com in /etc/hosts
https://bugs.launchpad.net/bugs/440762
You re
** Changed in: vm-builder (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
make sure source is obtainable for uec kernel images
https://bugs.launchpad.net/bugs/444605
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Changed in: vm-builder (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
rename uec kernel/ramdisk for automated downloading or easier doc
https://bugs.launchpad.net/bugs/444598
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: vm-builder (Ubuntu Karmic)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: vm-builder (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
ec2-images have ubuntu.canonical.com in /etc/hosts
https://bugs.launchpad.net/bugs/440757
You received th
fix-released in 1.3-34544-0ubuntu3 .
Additionally, I got some feedback from a amazon developer indicating that they
will include this in future releases.
** Changed in: ec2-ami-tools (Ubuntu)
Status: Confirmed => Fix Released
--
ec2-bundle-image and ec2-unbundle-image use single, static
A couple options here are:
- symlinks
ubuntu-uec-amd64-kernel -> ubuntu-uec-karmic-amd64-vmlinuz-2.6.31-11-server
ubuntu-uec-i386-ramdisk ->
ubuntu-uec-karmic-i386-initrd.img-2.6.31-11-generic-pae
- LATEST (or otherwise named) file containing:
ubuntu-uec-amd64-kernel ubuntu-uec-karmic-amd64
updated copy and paste for hardy image build on ec2 instance.
This uses karmic beta, and removes any references to external patches.
** Attachment added: "updated copy and paste for hardy image build on ec2
instance"
http://launchpadlibrarian.net/33250260/hardy-refresh.txt
--
ec2: Build new
On Wed, 7 Oct 2009, Dustin Kirkland wrote:
> Or a tarball of all of the pertinent pieces?
That would be possible, yes, but even inside the tarball, you'd want to
provide predictable names, or a mechanism to obtain the names.
All a simply-named tar file does is move the problem to the local syste
Oh yeah, the benefit of this script over the other is that it creates a
new filesystem rather than resizing an existing one. This overcomes the
one negative of a 2G image that I could think of, in that an 'mke2fs'
for a 2G filesystem would possibly create fewer inodes than would
reasonably be used
adding another resize-uec-image script.
This script should work for extending or shrinking an image. At this
point I'm leaning towards creating 2G images for uec output, and
resizing them up to 10G before bundling for ec2 with this script here.
the 2G images are much more easy to work with, and
** Changed in: vm-builder (Ubuntu)
Status: Triaged => Fix Committed
--
UEC images could be smaller
https://bugs.launchpad.net/bugs/439868
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I just verified that resizing an image now also increases number of
inodes.
$ truncate my.img --size 1M
$ mke2fs -F my.img >/dev/null
mke2fs 1.41.9 (22-Aug-2009)
$ dumpe2fs my.img | grep 'Inode count'
dumpe2fs 1.41.9 (22-Aug-2009)
Inode count: 128
$ truncate my.img --size 100M
$ resi
hopefully final resize script. I know this is a bad place for revision
control, so hopefully this will be the last thing put here. Then, we'll
put this somewhere in bzr.
Newly attached version:
- works to increase or decrease size of filesystem
- catches errors and gives error messages (rather
On Fri, 9 Oct 2009, Thierry Carrez wrote:
> The official branch is at lp:uec-tools
> https://code.launchpad.net/~ubuntu-core-dev/uec-tools/ubuntu
>
> Can it handle the new default .img.tar.gz format ? At first look it
> seems it handles only .img or .img.gz...
I can make it do that, but personall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I thought I saw a bit of code which somebody (mdz?) wrote to collect
> relevant information from an EC2 instance. If anybody remembers where
> this went, perhaps it could be attached to this bug.
mdz had done some work on this, I know that he point
** Changed in: vm-builder (Ubuntu Karmic)
Status: Triaged => Fix Released
--
UEC images could be simpler to download and bundle
https://bugs.launchpad.net/bugs/444598
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I just verified this is functioning correctly, creating bug 447325 on
ec2 karmic beta.
** Changed in: ec2-init (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: apport
Status: In Progress => Fix Released
--
need apport hooks for ec2-init
https://bugs.launchpad.net/bugs/41
Public bug reported:
Binary package hint: apport
just testing ubuntu-bug on ec2.
i ran ubuntu-bug apport
ProblemType: Bug
Architecture: amd64
Date: Fri Oct 9 15:38:57 2009
DistroRelease: Ubuntu 9.10
Ec2AMI: ami-5ebe5d37
Ec2AMIManifest: canonical-cloud-us/karmic-x86_64-beta.manifest.xml
Ec2Avail
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/33363634/Dependencies.txt
** Changed in: apport (Ubuntu)
Status: New => Invalid
--
testing a ubuntu-bug report on ec2
https://bugs.launchpad.net/bugs/447325
You received this bug notification because you are a membe
closing this, it was only done to test bug 415019.
--
testing a ubuntu-bug report on ec2
https://bugs.launchpad.net/bugs/447325
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
i think the use case of downloading a .tar.gz file and then resizing it
to an image to upload is probably not that common.
That said, i added code for it. I've also put this into a branch so it
at least can be somewhat controlled.
I doubt that its the best place for it, but it needs to go somewh
** Also affects: ubuntu-on-ec2/karmic
Importance: Undecided
Status: New
** Changed in: ubuntu-on-ec2
Importance: Undecided => Medium
** Changed in: ubuntu-on-ec2/karmic
Importance: Undecided => Medium
** Changed in: ubuntu-on-ec2/karmic
Status: New => Confirmed
** Changed
unfortunately, the above strace are of upstart (start / restart), not of
'cron'. upstart is hanging when it tries to start cron. I'd like to
see why cron isn't starting. Thats why I asked for 'strace cron' rather
than upstart.
--
The cron daemon does not start (hangs on "start cron")
https://b
Torsten,
I'm somewhat confused... The description of this bug mentions euca-register,
but comment 4 fairly clearly says 'ec2-register'.
Which are you using?
--
ec2-bundle-vol and ec2-upload-bundle result in non accepted manifest
https://bugs.launchpad.net/bugs/470355
You received this bug not
> I think this might be more of a problem with ec2-init.
Just to be clear on what is happening here:
- eucalyptus is intending to provide an ec2 compatible meta-data service
(described at
http://docs.amazonwebservices.com/AWSEC2/2009-04-04/DeveloperGuide/ ).
that includes a field "local-hostn
Confirming this:
$ printf "%s\n%s\n" '#!/bin/sh' 'echo hello world" > /tmp/user-data.sh
$ euca-run-instances -k mykey --user-data-file /tmp/user-data.sh emi-220011A6
-t m1.small
$ euca-describe-instances
RESERVATION r-342805FE admin default
INSTANCEi-3BB70743 emi-220011A6
I believe I've verified that using euca-run-instances base64 encodes data 2
times rather than once.
For example, with euca2ools configured to run against ec2, I do:
$ euca-run-instances --user-data "hello world" --key ec2-keypair ami-ef00e386
$ ssh ${ec2_host} 'wget -q http://169.254.169.254/late
This is just to collect information about ephemeral storage on UEC and
ec2.
on ec2, instance types are described at:
http://docs.amazonwebservices.com/AWSEC2/latest/DeveloperGuide/index.html?instance-types.html
type | arch | ephemeral disk| mounted ?
-
I collected information on ec2 by starting up an instance of each type,
and then running:
for host in ${host_list}; do
ssh -i my-key.pem ubu...@${host} sh < ~/t/fs-info.sh
done 2>&1 | tee output.txt
fs-info.sh is attached here.
** Attachment added: "fs-info: collect filesystem info on ec2"
h
for reference, i'm also attaching output of the above:
** Attachment added: "output.txt: output of fs-info.sh on each instance type"
http://launchpadlibrarian.net/34419663/output.txt
--
UEC images do not mount ephemeral disk on /mnt at boot
https://bugs.launchpad.net/bugs/458850
You received
A bit more data...
I'm fairly sure that the correct thing to do here is just to remove the
following two lines from main() in euca-run-instances:
|if user_data:
|user_data = base64.urlsafe_b64encode(user_data)
Also 'import base64' on line 37 could then be removed as this is
** Changed in: ec2-init (Ubuntu Karmic)
Milestone: None => ubuntu-9.10
--
ec2: ssh public key fingerprint in console output does not match EC2 standards
https://bugs.launchpad.net/bugs/458576
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
** Attachment added: "suggested patch"
http://launchpadlibrarian.net/34426390/fix.debdiff
--
ec2: ssh public key fingerprint in console output does not match EC2 standards
https://bugs.launchpad.net/bugs/458576
You received this bug notification because you are a member of Ubuntu
Bugs, which
I attached suggested patch for this to bug 458576 "suggested fix".
http://launchpadlibrarian.net/34426390/fix.debdiff
--
UEC images do not mount ephemeral disk on /mnt at boot
https://bugs.launchpad.net/bugs/458850
You received this bug notification because you are a member of Ubuntu
Bugs, which
The above can/should be tested by starting an instance, then:
sudo cp /etc/fstab /etc/fstab.dist
sudo dpkg -i ec2-init_0.4.999-0ubuntu7_all.deb
diff -u /etc/fstab.dist /etc/fstab
# you should see that (bug 458850)
# i686:
# device /dev/sdb changed to /dev/sda2
# both i686 x86_64:
# ext2 -> ext3
first 'suggested fix' did not get ssh keys written to console because
stderr wsan't redirected through the 'tee /dev/console'. This does.
** Attachment added: "suggested patch 2"
http://launchpadlibrarian.net/34426991/fix.debdiff
--
ec2: ssh public key fingerprint in console output does not
clean version of 2. (previous patch had 'fix.debdiff' recursively
included')
** Attachment added: "suggested patch 3"
http://launchpadlibrarian.net/34428013/fix.debdiff
--
ec2: ssh public key fingerprint in console output does not match EC2 standards
https://bugs.launchpad.net/bugs/458576
Yo
in comment 8, i should have mentioned, you may still see 'mountall'
errors from boot, complaining about lack of /dev/sdb. thats to be
expected as /etc/fstab had that, and we cant overwrite it before
mountall runs.
also, you can verify in both UEC and ec2 /mnt should be mounted.
--
ec2: ssh publi
** Changed in: euca2ools (Ubuntu Karmic)
Milestone: None => karmic-updates
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: karmic-updates => None
** Changed in: euca2ools (Ubuntu Karmic)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: euca2ools (Ubun
Fixed in 20091027 daily, verified as below:
$ euca-describe-instances i-62de5f0a
RESERVATION r-fe768596 950047163771default
INSTANCEi-62de5f0a ami-a50ae9cc
ec2-67-202-43-236.compute-1.amazonaws.com
domU-12-31-39-0A-0A-31.compute-1.internal running
The following shows that this did not regress the mounting of /mnt on
20091027 build that included this fix.
$ printf "%s: %s\n" $(wget -O - -q 169.254.169.254/latest/meta-data/ami-id) \
$(wget -O - -q http://169.254.169.254/latest/meta-data/ami-manifest-path )
ami-cb0ae9a2:
ubuntu-images-test
Verified on both i686 and x86_64 on
$ uname -m
i686
$ printf "%s\n" $(wget -O - -q
http://169.254.169.254/latest/meta-datainstance-type)
c1.medium
$ grep mnt /etc/fstab
/dev/sda2/mntext2defaults0 0
$ df /mnt
Filesystem 1K-blocks Used Available Use%
I'm also unable to reproduce Markus's problems with --user-data ' << FOO
>' and a patched euca2ools.
I've built a ppa build of euca2ools with the patch at
https://launchpad.net/~smoser/+archive/ppa .
I tested that the patch works against ec2 with user data of " << FOO >",
and that it fails agains
I just verified that ec2-api-tools work with such user data when pointed at a
eucalyptus server:
$ ec2-run-instances -k mykey --user-data " << FOO >" emi-247011C0
RESERVATION r-45F60808 admin admin-default
INSTANCEi-523209EF emi-247011C00.0.0.0 0.0.0.0 pending mykey 0
I'm attaching a snippit from /var/log/eucalyptus/cloud-error.log, that
occurs when you run the failing euca-run-instances command above.
** Changed in: eucalyptus (Ubuntu Karmic)
Status: Invalid => Confirmed
** Changed in: eucalyptus (Ubuntu Karmic)
Milestone: None => karmic-updates
*
On Tue, 27 Oct 2009, Neil Soman wrote:
> You said "I'm also unable to reproduce Markus's problems with --user-
> data ' << FOO >' and a patched euca2ools."
That should have said "*able* to reproduce" . I do see it.
To reproduce, you have to
a.) fix euca2ools so that it doesn't doubly encode use
This definitely would be nice. Because I've been delinquent on getting
a replacement for ec2-version-query, its really not possible right now.
At some point, I hope to be producing something on s3 storage that is
web accessible and laid out like ec2-version-query, so this would be
easier to do.
On Wed, 28 Oct 2009, jberryman wrote:
> Will this be fixed in Jaunty or will that package remain broken?
With such an easy workaround (export JAVA_HOME=/usr), this bug doesn't
really fit the criteria for Stable Release Updates
(https://wiki.ubuntu.com/StableReleaseUpdates).
So, yes, it will like
> Note that python-boto does encode UserData using base64.b64encode
> (not urlsafe_b64encode as suggested in comment 13).
Thierry is correct. The commenter in comment 13 above must have been
staring at a computer screen too long. boto uses base64.b64encode
everywhere that i can see:
http://code
Marking this fix-commited. I've backported ec2-init 0.4999 from
karmic's version to hardy (0.4.999-0ubuntu5~hardy1) and that is
available in the ubuntu-on-ec2 ppa (https://launchpad.net/~ubuntu-on-
ec2/+archive/ppa?field.series_filter=hardy).
Images are available on ec2 with the necessarily chang
Also, wanted to mention here. I had email conversation here with Martin
from rightscale. The backport of ec2-init removes the rightscale-init
script that the old package included. He said this was fine with them,
that they can make use of the user-data script functionality as they're
doing in ka
Just for informational purposes, the way that bug 458850 was fixed, if
updates are done to Eucalyptus such that ephemeral storage is on
/dev/sdb instead of /dev/sda2 ec2-init should correctly adjust.
--
x86_64 images should be presented a /dev/sdb, not a /dev/sda2
https://bugs.launchpad.net/bugs/
** Changed in: ec2-init (Ubuntu)
Status: Confirmed => Fix Released
--
Wait for network before downloading ssh credentials or user-data
https://bugs.launchpad.net/bugs/308530
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Public bug reported:
Booting a karmic kernel under xen crashes very early in the boot
process.
This is a duplicate of Red Hat bug 508120
(https://bugzilla.redhat.com/show_bug.cgi?id=508120).
At very least, our kernels at the moment do not have the two fixes mentioned
there,
http://git.kernel.
just a note, the RH bug also mentions http://lkml.org/lkml/2009/8/21/71
, (fix at http://lkml.org/lkml/2009/8/21/128).
--
2.6.31-rc1 xen domU crashes early during boot
https://bugs.launchpad.net/bugs/419315
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
Public bug reported:
Binary package hint: ec2-api-tools
ec2min, ec2umin, ec2-monitor-instances, ec2-unmonitor-instances do not have
EC2_HOME set. As such, running them results in death like:
$ ec2-monitor-instances
/usr/bin/ec2-monitor-instances: line 9: EC2_HOME: EC2_HOME is not set
$ grep
** Changed in: ec2-api-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
ec2-monitor-instances, ec2-unmonitor-instances fail with 'EC2_HOME not set'
https://bugs.launchpad.net/bugs/419464
You received this bug notification because you are a member of Ubuntu
B
Public bug reported:
Binary package hint: qemu-kvm
I was running a jaunty kvm guest with the following command line:
$ kvm -m 512 -hda jaunty-desktop-i386.img \
-hdb jaunty-desktop-i386-swap.img -boot c \
-net nic,vlan=0 -net
user,vlan=0,hostfwd=tcp:127.0.0.1:59000-:5900,hostfwd=tcp:127.0.
** Attachment added: "BootDmesg.gz"
http://launchpadlibrarian.net/30878835/BootDmesg.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/30878836/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/30878837/Dependencies.txt
** Att
I'll make this argument one last time, then I promise to let it be.
I believe that the correct fix for this bug is the attached patch below.
What it does, is simply put comment headers in the files that are
modified by ec2-set-defaults to inform the user that they should be
modifying the template
I just wanted to post some progress here. I have verified that the
latest vmbuilder (trunk) and other relavant code pieces are able to
build a hardy image. the instructions for doing so are in the attached.
** Attachment added: "copy and paste instructions on how to create hardy image"
http:/
simpler change, simply put the headers in the template files rather than
generating them on the fly.
** Attachment added: "modify template files in revision control directly"
http://launchpadlibrarian.net/32625522/bug414997-modify-template-files.diff
--
ec2-set-defaults should be 'run_once_pe
The issue with the above patches (comment 6 and comment 7) is that they
possibly trump changes the user made that they intended to cross the re-
bundling. If the user made the change with a tool, then they possibly
wouldn't see the file and warning that was written in it. Such an
example is that
At the moment, I think there is no obvious solution here. I think I'm
pretty much at the conclusion that we should put a header in the
template files below, and not change anything else.
If the user wants to have the template system run on re-bundle, then they
should simply remove the lock file
Here's where I've ended up. I think the most sane thing at the moment
is to simply document the current behavior.
** Attachment added: "simply document current behavior"
http://launchpadlibrarian.net/32628222/bug414997-simply-document-current-behavior.diff
--
ec2-set-defaults should be 'run
On Mon, 28 Sep 2009, Eric Hammond wrote:
> Scott: What do you mean by "not change anything else"? If the user
> modifies sources.list would a rebundled AMI overwrite their changes or
> not?
I meant that we should leave ec2-init behavior as it is right now, with
'run-once-ever' for ec2-set-defaul
I'm removing the milestone for this. As I've personally come to the
conclusion that it is mostly functioning as it should.
** Changed in: ec2-init (Ubuntu)
Milestone: ubuntu-9.10-beta => None
--
ec2-set-defaults should be 'run_once_per_ami'
https://bugs.launchpad.net/bugs/414997
You received
I just uploaded to canonical-testing-us:
aki-80a84be9 ubuntu-kernel-2.6.31-300.3-ec2-i386.manifest.xml
aki-8aa84be3 ubuntu-kernel-2.6.31-300.3-ec2-x86_64.manifest.xml
ari-90a84bf9 ubuntu-ramdisk-2.6.31-300.3-ec2-i386.manifest.xml
ari-8ea84be7 ubuntu-ramdisk-2.6.31-300.3-ec2-x86_64.m
On Tue, 29 Sep 2009, Etienne Goyer wrote:
> Dustin Kirkland wrote:
> > Note that I had to modprobe acpiphp. Perhaps we should consider loading
> > this module in init or in modules.conf.
>
> I have reported this issue in bug #364916.
Well, specifically in that bug you reported that there was no
> Another option that would work is CONFIG_HOTPLUG_PCI_ACPI=y (as Etienne
> originally suggested)
Per Tim Gardner in irc:
smoser, I think you're gonna have to go the initramfs route.
i accept your answer, but just curious, why not build in?
smoser, regression potential for existing platforms. i
Public bug reported:
Below is a snippit of output for a AMI, AKI, ARI tripplet from from 'ec2
-describe-images -a' and 'euca-describe-images -a' respectively. Note
that the euca-describe-images output does not list the aki and ari that
are paired with the ami. This output is both useful and poss
901 - 1000 of 8709 matches
Mail list logo
