For reference, this article enumerates the steps I took to run
vmbuilder:
http://alestic.com/2010/01/vmbuilder-ebs-boot-ami
--
Too much image copying when using vmbuilder for EC2
https://bugs.launchpad.net/bugs/502495
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
I'm using the latest lp:vmbuilder source to build EBS boot AMIs for EC2.
I noticed that there is an awful lot of image file copying being done
which seems unnecessary when using vmbuilder for this purpose.
1. vmbuilder installs the image files into a temporary "root" subdirec
No sooner entered as a bug than I think I've tracked this down to an
invalid "part" file I was using:
root 10240 a1
root 2048 a1
/mnt 1 b
Note the extra "root" entry.
I don't know if this can be used to create validation code to prevent
other people from making this dumb mistake, but I'm m
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36525905/Dependencies.txt
--
vmbuilder: Creates mostly empty EC2 images on 64-bit
https://bugs.launchpad.net/bugs/493510
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Public bug reported:
I'm using vmbuilder on 32-bit and 64-bit EC2 instances with identical
arguments except for --arch, --kernel, and --ramdisk. The 32-bit EC2
images are created fine, but the 64-bit images are practically empty
except for a few /var directories.
I have tracked this down to the
Set to "Confirmed" since Scott confirmed the bug. Setting to "Medium"
since this seems like a severe impact on a non-core application.
** Changed in: vm-builder (Ubuntu)
Status: New => Confirmed
** Changed in: vm-builder (Ubuntu)
Importance: Undecided => Medium
--
vmbuilder: Deletes
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36488152/Dependencies.txt
--
vmbuilder: Deletes most of /dev on interrupt
https://bugs.launchpad.net/bugs/493020
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
In case it matters, I ran ubuntu-bug on the Karmic instance right before
I ran the vmbuilder command so that all of the information in this bug
would be captured from the system. Attempts to run ubuntu-bug fail
after /dev is cleared out.
--
vmbuilder: Deletes most of /dev on interrupt
https://bu
On IRC, smoser noted that he had also seen this behavior "on nectarine".
--
vmbuilder: Deletes most of /dev on interrupt
https://bugs.launchpad.net/bugs/493020
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:
I'm running vmbuilder on the latest EC2 Karmic AMI. When I Ctrl-C
interrupt the run, it deletes almost all of the devices in /dev making
the system somewhat unusable.
Here's a log demonstrating this. I have reproduced the problem on a
fresh AMI by interrupting it in about t
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35962327/Dependencies.txt
--
vmbuilder: --execscript in current directory is not found
https://bugs.launchpad.net/bugs/486955
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
This problem happens with the vmbuilder on trunk.
When running vmbuilder I passed in an option like
--execscript setup-karmic-server
where "setup-karmic-server" was an executable file in my current
directory.
vmbuilder output the following messages which give a warm fuzz
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/35962337/Dependencies.txt
--
vmbuilder: --ec2-bundle triggers "AttributeError: 'Ubuntu' object has no
attribute 'suite'"
https://bugs.launchpad.net/bugs/486956
You received this bug notification because you are a member of
Public bug reported:
This problem happens using vmbuilder on trunk.
When I specify --ec2-bundle (see entire command below) and I do not
specify --ec2-kernel and --ec2-ramdisk, then the following error is
generated:
2009-11-23 04:32:58,233 DEBUG : Oh, dear, an exception occurred
2009-11-23 04:3
Scott: Since you're solving this with an exec script, could you also
remove the incorrect /etc/hostname file while you're at it?
Even though I haven't found any standard packages which depend on
/etc/hostname it still bugs me to have an incorrect value stored there
by default.
--
ec2-images have
Thierry: Half joking, I'll point out that anybody can have root on an
Ubuntu system for an hour for only $0.10 with EC2.
More seriously: If the benefit of the rsync approach is only to increase
the number of inodes, perhaps the original mke2fs could be run with the
-N option to increase the number
AMIs for Amazon EC2 should be 10 GB (10240 * 1024 * 1024 bytes)
--
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-b...@lists.ubuntu.c
Here is the current documentation for user-data scripts:
http://alestic.com/2009/06/ec2-user-data-scripts
And the original, reference implementation (run at S71 on Ubuntu):
http://ec2-run-user-data.notlong.com
RightScale has completely different specs for how user-data is handled
in their enviro
I suggest this ability to support the ec2-* names should be a
requirement before the ec2-ami-tools on the Canonical EC2 images are
replaced with euca2ools (assuming euca2ools is sufficiently compatible
and stable for it to become the default).
It's not just Canonical's documentation which would be
The ideal solution would include the ability to easily set up either of
the following environments and be able to switch between them:
1) euca2ools without ec2-* symlinks. Optionally, Amazon's ec2-*-tools
packages could be installed alongside and commands from either set of
tools could be run ind
I think this is necessary to be completed for Canonical's images to
replace the ones I've been building, but given its place in the whole of
Ubuntu, I'm marking it Medium importance.
** Changed in: ec2-init (Ubuntu)
Importance: Undecided => Medium
--
ec2-init: Move ec2-run-user-data to startu
** Changed in: ec2-init (Ubuntu)
Importance: Undecided => Low
--
rightscale init script
https://bugs.launchpad.net/bugs/434181
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
h
** Changed in: ec2-init (Ubuntu)
Status: New => Confirmed
--
rightscale init script
https://bugs.launchpad.net/bugs/434181
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b...@lists.ubuntu.com
h
Based on IRC discussion, it may not have been clear that I consider this
a reasonably important bug to fix for Karmic even though it means
splitting ec2-init into two init scripts. There are existing
architectures using Ubuntu on EC2 which break when attempted to be run
on Canonical's latest Karmi
Could you provide details or pointers to the appropriate code? (I'm
also incorporate these into some images I build for clients.)
--
rightscale init script
https://bugs.launchpad.net/bugs/434181
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Perhaps another approach might be to say that the user-data script
functionality is entirely based on the current implementation in the
AMIs on http://alestic.com which run the user-data late in the boot
process. With that as the de-facto standard, then to enable easy
migration for existing users,
Until we figure out the ultimate flexible solution, I'd like to be able
to log in while the user-data script is running so I can monitor
progress and debug.
A security bug in ssh should be considered a good motivating reason to
publish updated AMIs.
--
ec2-init: Move ec2-run-user-data to startup
Public bug reported:
Binary package hint: ec2-init
AMI: ami-a40fefcd canonical-alphas-us/karmic-i386-alpha5.1.manifest.xml
All of the ec2-init functionality is currently driven by a single
/etc/init.d/ec2-init script which is run at a single rc startup level
(S15).
Some of the functionality, li
** Changed in: vm-builder (Ubuntu)
Status: New => Confirmed
** Changed in: vm-builder (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
--
ec2: Include kernel modules in AMIs
https://bugs.launchpad.net/bugs/429169
You received this bug notification because you are a member of U
> there presumably aren't very many modules for the EC2 kernel.
I guess this raises the questions of what modules we are talking about,
and this is an area where I wouldn't know what to cut out. I personally
depend on some which may not be considered part of the core modules
including: fuse, xfs,
Public bug reported:
It is fairly standard practice to include kernel modules in images for
Amazon EC2, but the most recent Karmic AMIs do not include them:
ami-a40fefcd
canonical-alphas-us/karmic-i386-alpha5.1.manifest.xml
ami-a20fefcb
canonical-alphas-us/karmic-x86_64-alpha5.1.manifest
A lot of work has been done on ec2-init in the last couple months. I'm
assuming that whatever the problem was here it has been fixed, since
we're not seeing issues in recent images. If there is still an issue,
please provide the requested details and set the status to "New".
** Changed in: ec2-
Is this description specific enough to be a bug report or should this be
moved into a proposal thingy (not sure of the exact Ubuntu process
terminology)?
--
Command to track which version of EC2 are we running.
https://bugs.launchpad.net/bugs/333860
You received this bug notification because you
Is this still a problem?
Can you provide an AMI id where it can be reproduced?
Can you elaborate on what you mean by "correctly"?
--
ec2 doesnt set /etc/apt/sources.list correctly
https://bugs.launchpad.net/bugs/402271
You received this bug notification because you are a member of Ubuntu
Bugs,
Soren:
There are a number of packages which do not activate automatically when
they installed, but instead require changing a configuration line in
/etc/default/xxx to "RUN=yes" or some such.
The vmbuilder EC2 plugin would have no trouble tweaking this after
installing the ec2-init package.
What
** Summary changed:
- ec2-init hangs waiting for ec2 meta-data service
+ ec2-init hangs boot on non-EC2/Eucalpytus systems
** Changed in: ec2-init (Ubuntu)
Status: New => Confirmed
--
ec2-init hangs boot on non-EC2/Eucalpytus systems
https://bugs.launchpad.net/bugs/424065
You received th
The ec2-init package should only be installed on an instance (or image)
which is used inside of Amazon EC2 or compatible environment
(Eucalyptus). End users should never install the ec2-init package
themselves as it is only useful when building images for EC2/Eucalyptus.
Are there any other packa
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 bug
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, but
I'm not saying it's not valuable. I'm not saying I personally oppose
it.
I am saying that it appears to violate what I understood to be a promise
from Ubuntu and that the implications should be considered carefully and
the policy should be discussed publicly before the feature is
implemented.
--
I believe I have heard rather strong statements from Canonical that
Ubuntu will never have "phone home" type data collection hooks to find
out how many people are running Ubuntu. Though the overt intent of this
proposal may be philanthropic, this sounds suspiciously like such a
feature.
I would h
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 to
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, wh
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 ar
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 build
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.
--
vm
> 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:
https://bugs.laun
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: &q
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 notif
** 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,
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 \
--suite=intrep
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=100&externalID=1663
the missing newline breaks a command like:
echo "/dev/sdh /vol xfs noatime 0 0" >> /et
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 o
53 matches
Mail list logo
