When the issue of package updates were raised, I believe the answer included
things like:
- The update is not immediately run on every Ubuntu installation
- The user has the ability to turn it off
- The user has the ability to decide which archives to use
[Again, I'm not fighting against this,
Gustavo: Note that the current enhancement proposal goes beyond just
EC2, but appears to also apply to Ubuntu images users run with
Eucalyptus on their own hardware at their own company.
--
[FFE] ec2-init should check for image upgrades
https://bugs.launchpad.net/bugs/423856
You received this
Architecture: i386
Dependencies:
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia wl
Package: linux None [modified: /var/lib/dpkg/info/linux.list]
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=en_US.UTF-8
Uname: Linux 2.6.28-15-server i686
UserGroups:
I have been experiencing what sounds like the same problem running
Ubuntu 9.04 Jaunty on a Dell Latitude 6500. apport-collect data added
above. The biggest problem I have seems to be when I click-hold the
left mouse button, touch-drag-release on the touchpad, then release the
left mouse button.
Public bug reported:
I've been using a Verizon USB727 (USB modem) with Ubuntu 9.04 Jaunty and
it works beautifully most of the time.
However, after a number of hours (or sometimes minutes) of usage, it
suddenly disconnects from the network. The full errors from syslog are
available on:
By won't fix I assume this means that it will not be possible to
upgrade an instance running an Intrepid/Jaunty AMI to Karmic and expect
it to keep running on the older Intrepid/Jaunty kernel. This makes
sense given the issues with the kernel and the inability to upgrade a
kernel on a running
Public bug reported:
Binary package hint: ec2-ami-tools
The package ec2-ami-tools is outdated on Hardy, Intrepid, Jaunty,
Karmic. This prevents the usage of the latest EC2 features.
** Affects: ec2-ami-tools (Ubuntu)
Importance: Undecided
Status: New
--
Updgrade ec2-ami-tools
Public bug reported:
Binary package hint: ec2-ami-tools
The package ec2-ami-tools is outdated on Hardy, Intrepid, Jaunty,
Karmic. This prevents the usage of the latest EC2 features.
** Affects: ec2-ami-tools (Ubuntu)
Importance: Undecided
Status: New
--
Updgrade ec2-ami-tools
See #407861 for a recommended approach to relying on DHCP for hostnames.
** Changed in: ec2-init (Ubuntu)
Status: New = Invalid
--
ec2 doesnt set /etc/hostname properly.
https://bugs.launchpad.net/bugs/402273
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
[karmic] udev requires new kernel, breaks on EC2
https://bugs.launchpad.net/bugs/397187
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Running the latest udev (144) on a Karmic EC2 instance causes the
network to not come back up after a reboot because of this problem
(Andreas found this out, but I confirmed and thought it was also worth
mentioning this severe effect in this bug). I'm not sure this is really
a udev bug; the right
Cap, Are you saying that you are able to apply a fix to a running Ubuntu
instance on EC2 and get vm-builder to work correctly for you (what AMI
and what steps)? Or, are you just assuming that #293067 probably
relates because of the description?
Note that the images listed on http://alestic.com
This is now ringing a bell with me. I ran into very similar behavior with
simple Perl calls spinning when building images on EC2 instances. It was back
in 2007 so I'm having a hard time remembering what the problem or solution
were, but the answer may be somewhere in this code (which now
Am I correct in understanding that this process works on your local
Ubuntu system, but fails when you run it on EC2 instances using various
official and unofficial AMIs? If so, then it sounds like it may be more
of a bug against the EC2 images and environment than against vmbuilder
itself.
--
I can't see a situation where the initial users's uid and gid wouldn't
be 1000.
This situation arises when vmbuilder is being used to build standard
images which are going to be used by other parties. For example, when
vmbuilder is used to build public images for Amazon EC2:
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
Set up a mirror based on zone
https://bugs.launchpad.net/bugs/317065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I suppose an instance could examine a traceroute to each of the mirrors
to see which one is closer, but I don't know if this is a reasonable
solution to determining availability zone.
--
Set up a mirror based on zone
https://bugs.launchpad.net/bugs/317065
You received this bug notification
There is currently no standard, reliable method for determining what
specific availability zone an EC2 instance is running in.
In fact, availability zone us-east-1a for one EC2 account may not be the
same availability zone as us-east-1a for another EC2 account. Amazon
assigns these names
Er, my examples should have read:
ec2-us-east-1.archive.ubuntu.com
or
us-east-1.ec2.archive.ubuntu.com
--
Set up a mirror based on zone
https://bugs.launchpad.net/bugs/317065
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
polvi: My first sentence was not well phrased. Yes, that command gives
you the name of the availability zone for the current account, but that
can't be easily matched up with the availability zone for a different
account since the names are assigned randomly for each account.
--
Set up a mirror
** Changed in: vmbuilder
Status: New = Invalid
** Changed in: vm-builder (Ubuntu)
Status: New = Invalid
** Summary changed:
- vmbuilder EC2: ec2-ami-tools patch for excluding persistent network files
+ ec2-ami-tools patch for excluding persistent network files
--
ec2-ami-tools
** Changed in: vm-builder (Ubuntu)
Status: New = Invalid
** Changed in: vmbuilder
Status: New = Invalid
** Summary changed:
- vmbuilder EC2: Install EC2 AMI tools on image
+ Install EC2 AMI tools on image
--
Install EC2 AMI tools on image
https://bugs.launchpad.net/bugs/308545
** Summary changed:
- vmbuilder EC2: Create AMIs with full 10GB root partition
+ Create AMIs with full 10GB root partition
--
Create AMIs with full 10GB root partition
https://bugs.launchpad.net/bugs/308535
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The fix has been merged into vmbuilder trunk
--
vmbuilder EC2: Retry ec2-upload-bundle on failures
https://bugs.launchpad.net/bugs/287860
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This no longer seems to be a problem with the latest Ubuntu kernel.
** Changed in: vmbuilder
Status: New = Fix Released
--
vmbuilder EC2: Install libc6-xen
https://bugs.launchpad.net/bugs/293067
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This no longer seems to be a problem with the latest Ubuntu kernel.
** Changed in: vm-builder (Ubuntu)
Status: New = Fix Released
--
vmbuilder EC2: Install libc6-xen
https://bugs.launchpad.net/bugs/293067
You received this bug notification because you are a member of Ubuntu
Bugs, which
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vmbuilder
Status: Fix Committed = Invalid
--
vmbuilder EC2: Check postinstall script commands failure
https://bugs.launchpad.net/bugs/292901
You received this bug
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vm-builder (Ubuntu)
Status: Fix Released = Invalid
--
vmbuilder EC2: Check postinstall script commands failure
https://bugs.launchpad.net/bugs/292901
You received this
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vmbuilder
Assignee: (unassigned) = Eric Hammond (esh)
Status: Fix Committed = Invalid
--
vmbuilder EC2: postinstall script should be executable
https
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vm-builder (Ubuntu)
Status: Fix Released = Invalid
--
vmbuilder EC2: postinstall script should be executable
https://bugs.launchpad.net/bugs/292891
You received this bug
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vmbuilder
Status: Fix Committed = Invalid
--
vmbuilder EC2: sub postinstall = sub post_install
https://bugs.launchpad.net/bugs/292888
You received this bug notification
The vmbuilder EC2 plugin now takes a completely different approach which
makes this report irrelevant.
** Changed in: vm-builder (Ubuntu)
Status: Fix Released = Invalid
--
vmbuilder EC2: sub postinstall = sub post_install
https://bugs.launchpad.net/bugs/292888
You received this bug
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
vmbuilder EC2: ec2-ami-tools patch for excluding persistent network files
https://bugs.launchpad.net/bugs/308548
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Also affects: ubuntu-on-ec2
Importance: Undecided
Status: New
--
vmbuilder EC2: Install EC2 AMI tools on image
https://bugs.launchpad.net/bugs/308545
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This is now working on vmbuilder trunk.
** Changed in: vmbuilder
Status: Fix Committed = Fix Released
--
vmbuilder EC2: AttributeError: 'EC2' object has no attribute 'destdir'
https://bugs.launchpad.net/bugs/301487
You received this bug notification because you are a member of Ubuntu
This is now working on vmbuilder trunk.
** Changed in: vm-builder (Ubuntu)
Status: Fix Committed = Fix Released
--
vmbuilder EC2: AttributeError: 'EC2' object has no attribute 'destdir'
https://bugs.launchpad.net/bugs/301487
You received this bug notification because you are a member of
The contents of /etc/fstab is now pushed off to the person invoking
vmbuilder using the --part option.
** Changed in: vmbuilder
Status: Fix Committed = Invalid
--
vmbuilder EC2: /etc/fstab should be different for 32-bit vs. 64-bit images
https://bugs.launchpad.net/bugs/296136
You
The contents of /etc/fstab is now pushed off to the person invoking
vmbuilder using the --part option.
** Changed in: vm-builder (Ubuntu)
Status: Fix Committed = Invalid
--
vmbuilder EC2: /etc/fstab should be different for 32-bit vs. 64-bit images
https://bugs.launchpad.net/bugs/296136
Public bug reported:
I'm not sure how to report a bug against the ec2-ami-tools package
available in intrepid multiverse but that's where this belongs.
When an AMI is run and the resulting instance is rebundled, the new AMI
is unusable if one of the following files is present:
Ubuntu
** Attachment added: ec2amitools.patch
http://launchpadlibrarian.net/20466005/ec2amitools.patch
** Also affects: vmbuilder
Importance: Undecided
Status: New
** Summary changed:
- vmbuilder EC2: ec2-ami-tools patch for
+ vmbuilder EC2: ec2-ami-tools patch for excluding persistent
Public bug reported:
This request may relate more to the images being built than to the
vmbuilder tool itself.
Most of the popular EC2 images are distributed with the EC2 AMI tools
installed.
Users may expect these to be installed and may find it inconvenient if
they are not provided.
One
Turns out this is already a problem and should be increased in priority.
When walking through the following tutorial,
http://developer.amazonwebservices.com/connect/entry.jspa?categoryID=100externalID=1663
the missing newline breaks a command like:
echo /dev/sdh /vol xfs noatime 0 0
Public bug reported:
This request does not really belong against the vmbuilder project but
rather applies to the Ubuntu images being built. They currently have
4GB root partitions (4096) which is arbitrarily and unnecessarily
limiting.
These images should be built with the maximum 10GB root
Public bug reported:
Running against vmbuilder trunk, I get a mkfs.ext3: Device size
reported to be zero error when I run with the following command. Full
debug output is attached. It looks like /sys isn't being treated as a
special file system.
./vmbuilder \
xen ubuntu \
** Attachment added: vmbuilder.log
http://launchpadlibrarian.net/20474374/vmbuilder.log
--
vmbuilder EC2: mkfs.ext3: Device size reported to be zero. (missing /sys
support?)
https://bugs.launchpad.net/bugs/308709
You received this bug notification because you are a member of Ubuntu
Bugs,
Perhaps this delta needs to be included? (not sure if it's sufficient)
http://bazaar.launchpad.net/~nijaba/vmbuilder/ec2exec/revision/284
--
vmbuilder EC2: mkfs.ext3: Device size reported to be zero. (missing /sys
support?)
https://bugs.launchpad.net/bugs/308709
You received this bug
Soren pointed out that Ubuntu doesn't need /sys in /etc/fstab
Building off of trunk without the /sys 0 line in the part file now
works!
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
Status: New = Invalid
--
vmbuilder EC2: mkfs.ext3: Device size
** Changed in: vmbuilder
Status: New = Fix Committed
--
vmbuilder EC2: postinstall script should be executable
https://bugs.launchpad.net/bugs/292891
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The fix is now on the following branch:
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
** Changed in: vmbuilder
Status: Confirmed = Fix Committed
--
vmbuilder EC2: Retry ec2-upload-bundle on failures
https://bugs.launchpad.net/bugs/287860
You received this bug notification because
) = Eric Hammond (esh)
Status: New = Fix Committed
--
vmbuilder EC2: AttributeError: 'EC2' object has no attribute 'destdir'
https://bugs.launchpad.net/bugs/301487
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
The fstab contents decision has been pushed off to the user with the --part
option in development on the following branch:
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Nick Barcet (nijaba)
Status: New = Fix
Fixes are meged into
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
and are ready to be merged into the trunk.
--
vmbuilder EC2: sub postinstall = sub post_install
https://bugs.launchpad.net/bugs/292888
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The changes in the following brand obviate the need for a postinstall script so
this bug is no longer relevant.
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
** Changed in: vmbuilder
Status: New = Fix Committed
** Changed in: vmbuilder
Assignee: (unassigned) = Eric Hammond
The development on the following branch has replaced the need for a postinstall
script, so this bug no longer applies.
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
--
vmbuilder EC2: postinstall script should be executable
https://bugs.launchpad.net/bugs/292891
You received this bug
Public bug reported:
When I run vmbuilder --ec2 ... on the latest code from this branch:
https://code.launchpad.net/~nijaba/vmbuilder/ec2exec
it fails with the following error. Let me know if you need additional
information to reproduce.
[...]
2008-11-24 00:37:42,564 DEBUGProcessing
Fixed in branch: https://code.launchpad.net/~esh/vmbuilder/ec2exec-fixes
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
Status: New = Fix Committed
--
vmbuilder EC2: AttributeError: 'EC2' object has no attribute 'destdir'
https://bugs.launchpad.net
Public bug reported:
When I use the --part option in vmbuilder --ec2 it builds an /etc/fstab
without a trailing newline on the last record.
This is probably just a minor nuisance and shouldn't affect much in the
way of functionality, but it also should be easy to fix.
I'm currently working off
I tried similar steps and it worked correctly this time.
I still have the commands which created the wrong branch sitting there
in a terminal so I know I didn't dream it. However, I can't reproduce
it at this time.
--
ec2exec: quotes not needed in sed command
Apparently I still have some learning to do with bzr and launchpad.net.
I tried to create the branch using:
bzr push lp:///~esh/vmbuilder/ec2exec-fixes-2
but instead it created:
https://code.launchpad.net/~ubuntu-ec2/vmbuilder/ec2exec-fixes-2
In any case, the fix works there.
--
ec2exec:
Taking this ticket since I am tired of having to restart 30+ minute
builds when a single piece of the bundle fails to upload.
** Changed in: vmbuilder
Assignee: Chuck Short (zulcss) = Eric Hammond (esh)
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh
I went the easy route and just added the --retry option to ec2-upload-
bundle
The fix is available on this branch:
https://code.launchpad.net/~esh/vmbuilder/ec2exec-fixes-2
** Changed in: vm-builder (Ubuntu)
Status: Confirmed = Fix Committed
--
vmbuilder EC2: Retry ec2-upload-bundle
Public bug reported:
vmbuilder --ec2 currently has a single template for /etc/fstab which is
based on the 64-bit /etc/fstab for EC2.
The exposed disks differ between 32- and 64-bit instances and they
should have different /etc/fstab setups to match what is advertised in
the EC2 documentation:
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
Status: New = Fix Committed
** Also affects: vmbuilder
Importance: Undecided
Status: New
** Changed in: vmbuilder
Status: New = Fix Committed
** Changed in: vmbuilder
Assignee
Public bug reported:
This change on the ec2exec branch:
http://bazaar.launchpad.net/~nijaba/vmbuilder/ec2exec/revision/276
causes this error:
2008-11-10 02:03:55,690 DEBUG['sed', '-i', 's/tty1/xvc0/',
'%s/etc/event.d/tty1']
2008-11-10 02:03:55,697 INFO sed: -e expression #1,
I'm starting to think it's bzr/launchpad's problem and not mine. I
subsequently did:
bzr push
in the same directory, and it went and created the correct branch which
I had originally requested:
Using saved location: bzr+ssh://[EMAIL
PROTECTED]/~esh/vmbuilder/ec2exec-fixes-2/
Created new
Chuck: Good to know, thanks.
Does this mean that libc6-xen is not needed or desired for running on
xen? If not, why is it even provided in Ubuntu?
--
vmbuilder EC2: Install libc6-xen
https://bugs.launchpad.net/bugs/293067
You received this bug notification because you are a member of Ubuntu
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
vmbuilder EC2: Install libc6-xen
https://bugs.launchpad.net/bugs/293067
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Based on a year of building and running Ubuntu images on EC2, the
community came to the following specific steps for managing libc6
issues:
chroot $imagedir apt-get install -y libc6-xen
echo 'hwcap 0 nosegneg' $imagedir/etc/ld.so.conf.d/libc6-xen.conf
chroot
** Changed in: vm-builder (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
vmbuilder EC2: sub postinstall = sub post_install
https://bugs.launchpad.net/bugs/292888
You received this bug notification because you are a
Of course I meant def instead of sub in the bug title. Sure I used
to program for a living in C, C++, Objective C, and many other languages
back in the day, but it has been Perl for the last 15 years, so bear
with me.
--
vmbuilder EC2: sub postinstall = sub post_install
Public bug reported:
The way that the EC2 plugin is currently designed, the post_install
portion wants to apt-get install openssh-server which attempts to
restart sshd and fails.
It would be nice if the post_install plugins were called before
unprevent_daemons_starting was invoked (currently in
** Changed in: vm-builder (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
vmbuilder EC2: Check postinstall script commands failure
https://bugs.launchpad.net/bugs/292901
You received this bug notification because you
** Changed in: vm-builder (Ubuntu)
Status: In Progress = Fix Committed
** Also affects: vmbuilder
Importance: Undecided
Status: New
--
vmbuilder EC2: postinstall script should be executable
https://bugs.launchpad.net/bugs/292891
You received this bug notification because you
Public bug reported:
If the exec script is missing the following error is given at the start
of the run:
The path to the --execscript file is invalid: SCRIPTNAME. Make sure
you are providing a full path.
It might be nice to also check to see if the script is executable and
provide a helpful
: Undecided
Assignee: Eric Hammond (esh)
Status: In Progress
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
** Changed in: vm-builder (Ubuntu)
Status: New = In Progress
--
vmbuilder EC2: sub postinstall = sub post_install
https
: Eric Hammond (esh)
Status: In Progress
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
Status: New = In Progress
--
vmbuilder EC2: postinstall script should be executable
https://bugs.launchpad.net/bugs/292891
You received this bug notification
-builder (Ubuntu)
Importance: Undecided
Assignee: Eric Hammond (esh)
Status: In Progress
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) = Eric Hammond (esh)
Status: New = In Progress
--
vmbuilder EC2: Check postinstall script commands failure
https
301 - 377 of 377 matches
Mail list logo
