filed upstream at https://eucalyptus.atlassian.net/browse/TOOLS-170
** Also affects: euca2ools
Importance: Undecided
Status: New
** No longer affects: euca2ools
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to euca2ools in
Blueprint changed by Scott Moser:
Work items changed:
Work items:
collect complete list Ubuntu server bits to be supported: TODO
- provide example metadata and data: TODO
- develop client for mirroring data: TODO
+ provide example metadata and data: DONE
+ develop client for mirroring data
** Changed in: cloud-init (Ubuntu Raring)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1090482
Title:
over-riding distro config still
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1073077
Title:
zsh complains about locale_warn on launch
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1049146
Title:
cloud-init runs again after reboot in release
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/978127
Title:
incorrect time on node causes failed oauth
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1018554
Title:
write timestamp to console on
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/974509
Title:
cloud-init selects wrong mirror with dns
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1028501
Title:
cloud-init selects wrong mirrors for arm
To
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1006963
Title:
sources.list configuration does not cover
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1037727
Title:
support adding region/availability to mirror
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077020
Title:
cloud-init ca-certs leaves a blank line in
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1080985
Title:
'noblock' setting for resize_rootfs is broken
fixed in -quantal proposed update 0.7.0-0ubuntu2.2
** Changed in: cloud-init (Ubuntu Quantal)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
verified in quantal upload 0.7.0-0ubuntu2.2 via the same way as
https://bugs.launchpad.net/cloud-init/+bug/1006963/comments/3
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1077700
Title:
Issue with ConfigDriveV2 and ssh
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: linux-lts-quantal (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Precise)
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu
Luis, for testing with -proposed, I used the attached following cloud-config
file passed in as user-data.
It adds -proposed and moves the ca-cert config module to run later in the
process so the update has already occurred.
Just for reference, I launched instance like this:
$ EC2PRE=euca-
** Attachment added: slightly simplified version of user-data, should work on
precise also
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1077020/+attachment/3478025/+files/my.ud
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Summary changed:
- Quantal does not boot on EC2
+ update-grub-legacy-ec2 ignores kernels named -generic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1005551
Title:
Public bug reported:
in order to use config drive, nova-compute requires genisoimage.
This is fixed in raring's packaging, but not in quantal or precise.
** Affects: nova (Ubuntu)
Importance: Medium
Status: Fix Released
** Affects: nova (Ubuntu Precise)
Importance: Medium
I've committed changes for this in a precise branch at
lp:~smoser/ubuntu/precise/cloud-init/sru . I have a ppa build of that
at https://launchpad.net/~smoser/+archive/cloud-init-test/ . Any
testing on that would be appreciated.
The plan is to move SRU this as soon as the current SRU moves to
I've committed changes for this in a precise branch at
lp:~smoser/ubuntu/precise/cloud-init/sru . I have a ppa build of that
at https://launchpad.net/~smoser/+archive/cloud-init-test/ . Any
testing on that would be appreciated.
The plan is to move SRU this as soon as the current SRU moves to
I've committed changes for this in a precise branch at
lp:~smoser/ubuntu/precise/cloud-init/sru . I have a ppa build of that
at https://launchpad.net/~smoser/+archive/cloud-init-test/ . Any
testing on that would be appreciated.
The plan is to move SRU this as soon as the current SRU moves to
I built a precise cloud-init with the 'start networking' removed and
tried starting an lxxc instace with that from current precise daily
(with mountall 2.36.3). This issue persisted.
Steve, did you tihnk this *should* be fixed in precise?
--
You received this bug notification because you are
this is confirmed on lucid if you boot a maverick or newer kernel with
it.
** Also affects: cloud-init (Ubuntu Lucid)
Importance: Undecided
Status: New
** Changed in: cloud-init (Ubuntu Lucid)
Status: New = Confirmed
** Changed in: cloud-init (Ubuntu Lucid)
Importance:
Alex has requested that any work done here support reading data from a
cdrom as well as from a disk drive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1037567
Title:
need
just for easy reference, the fix was applied to trunk at revno 237
http://paste.ubuntu.com/1517992/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/611137
Title:
cc_mounts may
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Milestone: None = 0.7.2
** Changed in: cloud-init
Importance: Undecided = Medium
** Changed in: cloud-init
Status: New = Triaged
--
You received this bug notification because you
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1090482
Title:
over-riding distro config still broken
To manage notifications about this bug go
I've verified on both.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1073077
Title:
zsh complains about locale_warn on launch
To manage notifications about this bug go to:
reproduces with:
#cloud-config
apt_update: True
apt_sources:
- source: ppa:smoser/ppa
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1100491
Title:
cloud-init 0.6.3-0ubuntu1.3
fixed with:
$ diff -u
/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_apt_update_upgrade.py.dist
/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_apt_update_upgrade.py
---
/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_apt_update_upgrade.py.dist
2013-01-16
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Critical
** Changed in: cloud-init (Ubuntu)
Status: New = In Progress
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
--
You received this bug notification because you are a member
** Description changed:
[Impact]
cloud-init can no longer process cloud-config that specify a 'packages'
value. This affects any tools (Juju, MAAS) that rely on cloud-init to
install various packages as part of its first-boot. This seems to
trigger when specifying apt_sources in
** Summary changed:
- [SRU] cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
+ [SRU] apt_sources broken in 0.6.3-0ubuntu1.3
** Summary changed:
- [SRU] apt_sources broken in 0.6.3-0ubuntu1.3
+ [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression]
** Tags added:
This bug appears only when using precise daily images.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1081660
Title:
If maas-enlist fails to reach a DNS server, the node will
I think this should be fix-committed as it is in proposed.
** Changed in: cloud-init (Ubuntu)
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
I'm attaching a user-data file that I've built to demonstrate this issue, and
that it is resolved.
Simply:
* launch an instance with the provided user-data
* ssh to instance. wait for /home/ubuntu/version/ directory to contain
'cloud-init-output.log', and then reboot
On ssh in, you'll see a
Just to make sure, I've verified this is fixed in the latest daily of
precise builds. Using the user-data attached above, ssh'd into
instance, and saw the following in 0.6.3-0ubuntu1.4/output.log.
cloud-init 0.6.3-0ubuntu1.4
== sources.list.d ===
total 4
-rw-r--r-- 1 root root 178 Jan 18
** Changed in: cloud-init (Ubuntu Quantal)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1090482
Title:
over-riding distro config
This was fixed in trunk in revision 760.
** Changed in: cloud-init
Status: Confirmed = Fix Committed
** Changed in: cloud-init
Assignee: (unassigned) = Scott Moser (smoser)
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Fixed in 0.7.1-0ubuntu5.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Low
** Changed in: cloud-init (Ubuntu)
Status: New = Fix Released
** Changed in: cloud-init (Ubuntu)
Assignee: (unassigned) = Scott Moser (smoser)
** Also affects: cloud-init (Ubuntu Precise
Blueprint changed by Scott Moser:
Work items changed:
Work items:
collect complete list Ubuntu server bits to be supported: TODO
provide example metadata and data: DONE
- develop client for mirroring data: INPROGRESS
- add hooks to client for {new,remove} items: TODO
+ develop client
** Also affects: upstart (Ubuntu)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu)
Status: New = Confirmed
** Changed in: upstart (Ubuntu)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team,
This was broken in the daily images after a newer version of open-iscsi was
uploaded to precise-updates.
That new version did not have fixes for 2 bugs that we had in the ephemeral
images:
* update resolvconf with settings found by ipconfig for the
interface that contains the iscsi-root
** Changed in: cloud-init
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1100920
Title:
In Ubuntu 12.10, the legacy 'user' cloud-config option
** Also affects: cloud-init (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Released
** Changed in: cloud-init (Ubuntu)
Status: New = Fix Released
** Also affects: cloud-init (Ubuntu Precise)
Importance: Undecided
Status:
I'm pretty sure that the trunk commit just works when applied to
quantal. I'm attaching a deb here and the patch that built it, mainly
for future reference.
I would appreciate feedback as to whether or not it works though. The reason
(i think) it just works without a config change as Clint
** Attachment added: deb for quantal with above patch applied
https://bugs.launchpad.net/ubuntu/quantal/+source/cloud-init/+bug/1100920/+attachment/3509038/+files/cloud-init_0.7.0-0ubuntu2.3%7Equantal%7Elp1100920_all.deb
--
You received this bug notification because you are a member of
** Description changed:
- Currently Cloud-Init requires the ConfigDrive to be available on an
- unpartitioned disk, not a CDROM drive. Windows doesn't recognise this
- type of devices and mounting them requires the extraction of the data
- from the raw disk to an ISO file to be mounted /
** Changed in: lxc (Ubuntu Precise)
Status: New = Triaged
** Changed in: lxc (Ubuntu Precise)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
** Also affects: lxc (Ubuntu Precise)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1045955
Title:
lxc-create -t ubuntu-cloud broken on
** Changed in: cloud-init
Importance: Undecided = Low
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/961142
Title:
chef 0.10: package installation: returned 100, expected 0
** Attachment added: example config drive disk (iso)
https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Description changed:
+ == Begin SRU Information ==
+ [Impact]
+ Cloud-init in 12.04 has an upstart job named 'cloud-init-nonet' that
+ calls 'start networking' explicitly. This was done to fix a boot
+ deadlock (bug 800824), but it was not the proper fix.
+
+ A much more correct fix is now
** Attachment added: example config drive disk (iso)
https://bugs.launchpad.net/cloud-init/+bug/1100545/+attachment/3509470/+files/disk.config.gz
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Description changed:
- We need to update the config-drive datasource to support config-drive-v2
- [1]. There is a document showing what the config-drive looks like at
- [2].
+ == Begin SRU Information ==
+ [Impact]
+ 'config-drive' is a mechanism for passing data from the hypervisor (or
+
** Description changed:
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
cloud platform) to the guest (instance). config-drive-v2 was implemented
in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu.
In
** Description changed:
== Begin SRU Information ==
[Impact]
'config-drive' is a mechanism for passing data from the hypervisor (or
- cloud platform) to the guest (instance). cloud-init as delivered in 12.10
+ cloud platform) to the guest (instance). cloud-init as delivered in 12.10
I have also uploaded to precise-proposed the same version that is in the
maas-ephemeral-images archive.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas-enlist in Ubuntu.
https://bugs.launchpad.net/bugs/1081660
Title:
If
verified using the test above, but instead of using the deb, patched to use
proposed like:
sudo ./bi/mount-callback-umount patched.img.dist -- \
env LANG=C chroot MOUNTPOINT sh -ec '
rel=$(lsb_release -sc)
echo deb http://archive.ubuntu.com/ubuntu $rel-proposed main \
** Description changed:
I use VMware vSphere Client's to manage my Ubuntu 12.04 cloud-image
based vm's. vSphere is able to display the console of the vm as it
boots but because the default kernel boot parameter is set to use
console=ttyS0 I can't see anything until booting is done unless
just an update, I uploaded cloud-init with this fix to precise-proposed on
2013-01-31.
We're just still waiting on SRU team review.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
For reference, it seems like devstack running on 3.3 or later kernel
will see this. I found it running on quantal:
adam_g smoser: devstack doesn't configure its networks as multi_host. my fix
only addresses the issue for multi_host networks, where its assumed the dhcp
server is alwasy running
The issue here is really that /tmp is getting cleaned after the above runs.
Then, the test harness is going looking for the file, but its long gone.
I'm not sure if its specifically a bug or not to rely on runcmd running after
/tmp cleaning has run. but it does seem like /tmp is being cleaned
** Summary changed:
- cloud-init parses yaml incorrectly
+ reload-configuration can confuse upstart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
** Description changed:
During a cloud image initialization, the service cloud-final is never
executed if the cloud-config script contains an upgrade directive and
upstart is part of the upgraded packages:
TESTCASE:
1. Download a cloud image from
** Description changed:
the overlayfs filesystem does not have inotify support.
As a result, upstart jobs added via config (#upstart-job), will not be
noticed if /etc/init is on a overlayfs filesystem.
cloud-init should probably reload upstart configuration if it adds a job.
This is
** Description changed:
- Example from failure: https://jenkins.qa.ubuntu.com/job/raring-server-
- ec2/ARCH=amd64,REGION=eu-west-1,STORAGE=ebs,TEST=multi-part-ud,label
- =ubuntu-server-ec2-testing/17/console
+ Under bug 1080841 we made cloud-init invoke 'initctl reload-
+ configuration' after it
** Attachment added: dmesg when 'initctl reload-configuration' is *not* used
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528559/+files/dmesg.no-reload.txt
** Changed in: cloud-init (Ubuntu)
Status: New = Confirmed
** Changed in: upstart (Ubuntu)
** Attachment added: dmesg when 'initctl reload-configuration' is used
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1124384/+attachment/3528558/+files/dmesg.reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Attachment added: dmesg with --debug when 'initctl reload-configuration' is
used
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528635/+files/dmesg-debug-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Attachment added: dmesg with --debug when 'initctl reload-configuration' is
*not* used
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+attachment/3528636/+files/dmesg-debug-no-reload.txt
--
You received this bug notification because you are a member of Ubuntu
Server
To reproduce outside of cloud, you can basically follow the blog post
that I've got at [1].
Using this user-data to make sure you can login:
#cloud-config-archive
- content: |
#!/bin/sh
echo $(date -R): user-script run === | tee /run/user-script.log
- filename: myjob.conf
content: |
I mistakingly posted recreate instructions at
https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1103881/comments/6 . they're not comletely irrelevant there,
but I did intend for that to go here.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
** Changed in: server-papercuts
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to xinetd in Ubuntu.
https://bugs.launchpad.net/bugs/43574
Title:
Needs Ubuntu-style init script
To manage
** Description changed:
+ == Begin SRU Information ==
+ [General Description]
+ Amazon's EC2 is a xen based cloud platform, the bootloader that is used is
'pvgrub'. pvgrub runs inside a xen instance, reads a /boot/grub/menu.lst file,
and loads the kernels specified there. It does not support
** Description changed:
== Begin SRU Information ==
[General Description]
Amazon's EC2 is a xen based cloud platform, the bootloader that is used is
'pvgrub'. pvgrub runs inside a xen instance, reads a /boot/grub/menu.lst file,
and loads the kernels specified there. It does not support
Verified. See below.
$ sudo apt-get update sudo apt-get install -y lxc
$ lsb_release -c
Codename: precise
$ dpkg-query --show lxc
lxc 0.7.5-3ubuntu66
$ sudo lxc-clone -o source-precise-amd64 -n patched
$ cat /var/lib/lxc/source-precise-amd64/rootfs/etc/cloud/build.info
build_name:
Verified using latest precise released images in us-east-1 EC2.
# ami-0145d268 us-east-1/ebs/ubuntu-precise-12.04-amd64-server-20130204
$ ec2metadata --ami-id
ami-0145d268
$ ec2metadata --availability-zone
us-east-1b
$ dpkg-query --show grub-legacy-ec2
grub-legacy-ec2 0.6.3-0ubuntu1.4
$ sudo
Verified by booting most recent released cloud-image for 12.04 under
raring kvm.
$
imgurl=http://cloud-images.ubuntu.com/releases/precise/release-20130204/ubuntu-12.04-server-cloudimg-amd64-disk1.img;
$
Verified using latest released 12.04 image from raring under kvm:
$
imgurl=http://cloud-images.ubuntu.com/releases/precise/release-20130204/ubuntu-12.04-server-cloudimg-amd64-disk1.img;
$
Verification done using latest released 12.04 cloud-image booting it
under kvm in raring.
$ sudo apt-get install genisoimage -y
$ bzr branch lp:~smoser/+junk/backdoor-image ./bi
$
** No longer affects: zsh (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1073077
Title:
zsh complains about locale_warn on launch
To manage notifications about this
** Changed in: cloud-init (Ubuntu)
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1016695
Title:
add console=tty1 to cloud-image
ami-0cdf4965 (us-east-1/ebs/ubuntu-quantal-12.10-amd64-server-20130206)
does not seem to exhibit this problem.
## show the problem exists
$ dpkg-query --show euca2ools
euca2ools 2.0.2-1ubuntu2
$ dpkg -L euca2ools | grep cert-ec2
/etc/ssl/certs/cert-ec2.pem
$ ls -l /etc/ssl/certs/cert-ec2.pem
$ rel=$(lsb_release -sc)
$ echo $rel
precise
$ echo deb http://archive.ubuntu.com/ubuntu $rel-proposed main universe |
sudo tee /etc/apt/sources.list.d/$rel-proposed.list
$ sudo apt-get update
$ apt-cache policy lxc
lxc:
Installed: (none)
Candidate: 0.7.5-3ubuntu67
Version table:
Blueprint changed by Scott Moser:
Work items changed:
Work items:
Package fast path installer: TODO
- Add fast path installer to maas-ephemeral ppa: TODO
- Add fast path installer to maas-ephemeral images: TODO
- Integrate support into MAAS for fast path installer: TODO
- Support installer
I've moved this to 'low' on vm-builder, and made it affect grub2 in ubuntu.
Hopefully cjwatson can tell me if I'm wrong.
Generally, though, grub-pc and grub conflict with each other, so the state you
got (with -pc uninstalled) is not terribly unreasonable.
fwiw, The ubuntu cloud images uses
** Description changed:
Under bug 1080841 we made cloud-init invoke 'initctl reload-
configuration' after it wrote a upstart job. This was necessary because
inotify is not supported on all filesystems (overlayfs being the one of
most current interst).
This seems to be causing
marking this 'wont fix'
/etc/cloud/build.info has the info on what image this was, but at this point
that is of very little use.
** Changed in: cloud-utils (Ubuntu)
Status: New = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Public bug reported:
Under bug 1096999, we added support to util linux 'partx' to update the
partition table information of a disk with a mounted partition. This
takes advantage of kernel feature in 3.8.0.
This actually removes the necessity of cloud-initramfs-growpart.
We can now put that
** Summary changed:
- growpart and cloud-utils should support growning mounted filesystem
+ growpart and cloud-utils should support growing mounted filesystem
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
** Changed in: cloud-utils
Status: New = Fix Committed
** Changed in: cloud-init
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1136936
Sean,
Thanks for the suggestion of handling SIGTERM. I wasn't sure it would work,
but in testing it does seem to.
I've verified that it works by booting a system, and looking in
/var/log/dmesg. You'll see something like:
$ grep init:.*cloud-init.*kill /var/log/dmesg
[ 13.207358] init:
fix-committed in trunk at revno 788.
** Also affects: cloud-init
Importance: Undecided
Status: New
** Changed in: cloud-init
Status: New = Fix Committed
** Changed in: cloud-init
Importance: Undecided = Low
--
You received this bug notification because you are a member of
--- cloudinit/CloudConfig/cc_apt_update_upgrade.py 2013-01-16 22:19:13
+
+++ cloudinit/CloudConfig/cc_apt_update_upgrade.py 2013-03-04 21:23:28
+
@@ -221,10 +221,8 @@
# this is used if cfg['system_info']['package_mirrors'] is not present
def_mirror_info = {
-
Hi,
rbasak asked me to update status here, so I'll try to do that.
The branches linked to this bug contain a patch and fix that works for me.
There are also packages in the ppa at
https://launchpad.net/~virtual-maasers/+archive/maas-updated-packages .
I'd like to hear back from others as
** Changed in: cloud-init
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1136936
Title:
growpart and cloud-utils should support
1 - 100 of 3129 matches
Mail list logo
