ec2-ami-tools patch for excluding persistent network files
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu on EC2 |
Invalid
|
Undecided
|
Unassigned | ||
| Beta3 |
Invalid
|
Undecided
|
Unassigned | ||
| VMBuilder |
Invalid
|
Undecided
|
Unassigned | ||
| ec2-ami-tools (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
| vm-builder (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
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
/etc/
Debian
/etc/
This *may* not be a problem with Intrepid (?), but it definitely is a problem with some previous releases. The attached patch makes sure that the ec2-bundle-vol command excludes these files so that the resulting image can be used no matter which distro or release it was running.
It is fine for this patch to be included in Intrepid and I would ask that it be included there since that archive is the current best place to go for this software if one is using Ubuntu or Debian.
Related branches
| Eric Hammond (esh) wrote | #1 |
| Changed in vmbuilder: | |
| status: | New → Invalid |
| Changed in vm-builder: | |
| status: | New → Invalid |
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ec2-ami-tools: | |
| status: | New → Fix Released |
| Chuck Short (zulcss) wrote | #3 |
| Changed in ubuntu-on-ec2: | |
| status: | New → Invalid |
This bug was fixed in the package ec2-ami-tools - 1.3-31057-0ubuntu1
---------------
ec2-ami-tools (1.3-31057-
* New upstream version. (LP: #310547)
* debian/
/etc/
/etc/
(LP: #308548)
* debian/
ec2-
-- Chuck Short <email address hidden> Tue, 13 Jan 2009 11:46:59 -0500