[Bug 1092585] Re: euca-run-instances incorrect man page option for --instance-count
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 Ubuntu. https://bugs.launchpad.net/bugs/1092585 Title: euca-run-instances incorrect man page option for --instance-count To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/1092585/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-image-access] Easy machine access to Ubuntu image and cloud data
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: INPROGRESS
add hooks to client for {new,remove} items: TODO
develop example hooks for populating ec2: TODO
document data format: TODO
--
Easy machine access to Ubuntu image and cloud data
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-image-access
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1090482] Re: over-riding distro config still broken
** 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 broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1090482/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073077] Re: zsh complains about locale_warn on launch
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1073077/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1049146] Re: cloud-init runs again after reboot in release upgraded instance
** 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 upgraded instance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1049146/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 978127] Re: incorrect time on node causes failed oauth
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/978127/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1018554] Re: write timestamp to console on halt/reboot/shutdown
** 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 halt/reboot/shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1018554/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 974509] Re: cloud-init selects wrong mirror with dns server redirection
** 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 server redirection To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/974509/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1028501] Re: cloud-init selects wrong mirrors for arm
** 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 manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1028501/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1006963] Re: sources.list configuration does not cover security
** 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 security To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1006963/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037727] Re: support adding region/availability to mirror selection
** 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 selection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1037727/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077020] Re: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
** 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 /etc/ca-certificates.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1077020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1080985] Re: 'noblock' setting for resize_rootfs is broken
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1080985/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1090482] Re: over-riding distro config still 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. https://bugs.launchpad.net/bugs/1090482 Title: over-riding distro config still broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1090482/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1076811] Re: Cloud-init modules do not reflect loaded config
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 subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1076811 Title: Cloud-init modules do not reflect loaded config To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1076811/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077700] Re: Issue with ConfigDriveV2 and ssh authorized_keys
** 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 authorized_keys To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1077700/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: Quantal does not boot on EC2
** 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 Precise) Importance: Undecided = High -- 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: Quantal does not boot on EC2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077020] Re: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
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- ubuntu-ec2-run quantal daily --dry-run
--user-data-file=/tmp/my.ud --key=brickies
# us-east-1/ebs/ubuntu-quantal-daily-amd64-server-20130109
euca-run-instances --user-data-file=/tmp/my.ud --key=brickies
--instance-type=t1.micro ami-ed21a884
Then, in console output and /var/log/cloud-init-output.log I see:
Cloud-init v. 0.7 running 'modules:final' at Wed, 09 Jan 2013 14:26:23 +.
Up 58.53 seconds.
Updating certificates in /etc/ssl/certs... Error opening Certificate
cert-ec2.pem
140485162526368:error:02001002:system library:fopen:No such file or
directory:bss_file.c:398:fopen('cert-ec2.pem','r')
140485162526368:error:20074002:BIO routines:FILE_CTRL:system lib:bss_file.c:400:
unable to load certificate
WARNING: cert-ec2.pem does not contain a certificate or CRL: skipping
1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.ddone.
The noise about invalid certificicate is due to bug 1085537.
Then, inside the instance:
$ ls -l /usr/lib/ssl/certs/ | grep -i cloud
lrwxrwxrwx 1 root root 23 Jan 9 14:26 b1d2b355.0 - cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 23 Jan 9 14:26 cbbf81bb.0 - cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 50 Jan 9 14:26 cloud-init-ca-certs.pem -
/usr/share/ca-certificates/cloud-init-ca-certs.crt
** Attachment added: user-data file appropriate for testing
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1077020/+attachment/3478023/+files/my.ud
--
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 /etc/ca-certificates.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1077020/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077020] Re: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
** 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 subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1077020 Title: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1077020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** 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: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1097879] [NEW] nova-compute missing dependency on genisoimage
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 Status: Triaged ** Affects: nova (Ubuntu Quantal) Importance: Medium Status: Triaged ** Changed in: nova (Ubuntu) Importance: Undecided = Medium ** Changed in: nova (Ubuntu) Status: New = Fix Released ** Also affects: nova (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: nova (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: nova (Ubuntu Precise) Status: New = Triaged ** Changed in: nova (Ubuntu Quantal) Status: New = Triaged ** Changed in: nova (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: nova (Ubuntu Quantal) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1097879 Title: nova-compute missing dependency on genisoimage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1097879/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037567] Re: need config-drive-v2 support
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 -updates. -- 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 config-drive-v2 support To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1037567/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
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 -updates. -- 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: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077020] Re: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
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 -updates. -- 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 /etc/ca-certificates.conf To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1077020/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1031065] Re: cloud-init-nonet runs 'start networking' explicitly
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 a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1031065 Title: cloud-init-nonet runs 'start networking' explicitly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 611137] Re: cc_mounts may need to translate device names for xvda or virtio
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: Undecided = Medium ** Changed in: cloud-init (Ubuntu Lucid) Assignee: (unassigned) = Jos Boumans (jib) -- 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 need to translate device names for xvda or virtio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/611137/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037567] Re: need config-drive-v2 support
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 config-drive-v2 support To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1037567/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 611137] Re: cc_mounts may need to translate device names for xvda or virtio
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 need to translate device names for xvda or virtio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/611137/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1099199] Re: [PATCH] support resizing btrfs filesystems
** 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 are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1099199 Title: [PATCH] support resizing btrfs filesystems To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1099199/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1090482] Re: over-riding distro config still broken
** 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 to: https://bugs.launchpad.net/cloud-init/+bug/1090482/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073077] Re: zsh complains about locale_warn on launch
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: https://bugs.launchpad.net/cloud-init/+bug/1073077/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
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 failing to process juju-generated userdata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
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 22:11:06.472490044 + +++ /usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_apt_update_upgrade.py 2013-01-16 22:11:08.208488640 + @@ -72,7 +72,7 @@ params = mirrors params['RELEASE'] = release params['MIRROR'] = mirror -errors = add_sources(cloud, cfg['apt_sources'], params) +errors = add_sources(cfg['apt_sources'], params) for e in errors: log.warn(Source Error: %s\n % ':'.join(e)) -- 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 failing to process juju-generated userdata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
** 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 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 failing to process juju-generated userdata To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: [SRU] cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated userdata
** 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 cloud-init.
[Test Case]
Create a userdata file:
cat /tmp/ud.txt
#cloud-config
apt_sources:
- {source: 'ppa:openstack-ubuntu-testing/folsom-trunk-testing'}
apt_update: true
apt_upgrade: false
packages: [python-novaclient]
END
- Boot a quantal or precise Ubuntu Cloud image, specifying the ud.txt as
- user-data:
+ Boot a precise daily Ubuntu Cloud image, specifying the ud.txt as user-
+ data:
euca-run-instances -k adam -t m1.tiny -f /tmp/ud.txt ami-04d
Allow instance to boot. Since MAAS provisiongs nodes on-the-fly, first
boot will have the affected cloud-init version and the attached
traceback in /var/log/cloud-init-output.log.
For cloud instances, its most likely running an older version of cloud-
init and the cloud-config was processed okay on first boot. To test the
affected version there, ssh to the machine:
# revert changes to system from initial cloud-init run.
$ sudo dpkg -P python-novaclient ;\
- sudo rm -rf
/etc/apt/sources.list.d/openstack-ubuntu-testing-folsom-trunk-testing-precise.list
;\
- sudo rm -rf /var/lib/cloud/*
+ sudo rm -rf
/etc/apt/sources.list.d/openstack-ubuntu-testing-folsom-trunk-testing-precise.list
;\
+ sudo rm -rf /var/lib/cloud/*
# Install cloud-init from precise-updates
$ sudo apt-get install cloud-init=0.6.3-0ubuntu1.3
# re-run cloud-init
$ sudo cloud-init start-local ; sudo cloud-init start; sudo cloud-init-cfg
all config ; sudo cloud-init-cfg all final
Observe traceback ending in TypeError: add_sources() takes at most 2
arguments (3 given), the expected package was not reinstalled.
Apply fix to
/usr/share/pyshared/cloudinit/CloudConfig/cc_apt_update_upgrade.py and re-run
cloud-init. Works as
expected, package is reinstalled.
[Regression Potential]
Minimal, simple one-line.
[Original Report]
Noticed juju deployed services were failing to come up using Juju+MAAS
and the newly released cloud-init SRU for 12.04. The node provisioned
thru MAAS okay, but after first boot did not have the required agents
installed. On further investigation, it looks like the required juju
packages were never installed. /var/log/cloud-init-output.log shows
the following traceback:
The key fingerprint is:
b4:83:ef:99:6e:65:15:a3:a3:a2:83:0b:f1:3c:62:7f root@test-08
The key's randomart image is:
+--[ECDSA 256]---+
| |
|o|
|. . o |
| o .o .|
|. . S. o |
| +o |
|o.+. . ..o |
|.oo.oE ..o |
| .o.. o=|
+-+
Generating locales...
en_US.UTF-8... up-to-date
Generation complete.
2013-01-16 16:32:56,919 - __init__.py[WARNING]: Traceback (most recent call
last):
File /usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py,
line 117, in run_cc_modules
cc.handle(name, run_args, freq=freq)
File /usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/__init__.py,
line 78, in handle
[name, self.cfg, self.cloud, cloudinit.log, args])
File /usr/lib/python2.7/dist-packages/cloudinit/__init__.py, line 326, in
sem_and_run
func(*args)
File
/usr/lib/python2.7/dist-packages/cloudinit/CloudConfig/cc_apt_update_upgrade.py,
line 75, in handle
errors = add_sources(cloud, cfg['apt_sources'], params)
TypeError: add_sources() takes at most 2 arguments (3 given)
2013-01-16 16:32:56,919 - __init__.py[ERROR]: config handling of apt-
update-upgrade, None, [] failed
2013-01-16 16:32:56,998 - cloud-init-cfg[ERROR]: errors running cloud_config
[config]: ['apt-update-upgrade']
errors running cloud_config [config]: ['apt-update-upgrade']
Attached are /var/log/cloud-init.log and the MAAS provided user-data
from /var/lib/cloud/instance/user-data.txt
--
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:
[SRU] cloud-init 0.6.3-0ubuntu1.3 failing to process juju-generated
userdata
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3
** 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: regression-update -- 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: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named ; ; connection timed out; no servers could be reached
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 be named ;; connection timed out; no servers could be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression]
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. https://bugs.launchpad.net/bugs/1100491 Title: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression]
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 directory named for the cloud-init version that was present on boot. Once that directory has 'cloud-init.log' in it, then you can reboot. The next boot should have the next version of cloud-init in it (ie, if instance had 0.6.3-0ubuntu1.1, then 0.6.3-0ubuntu1.3 should be installed. If 0.6.3-0ubuntu1.3 was there , then -proposed should have been installed). Just looking at the associated logs will show if there as an error. I've verified using a daily image, that had 0.6.3-0ubuntu1.3 in it. (ebs/ubuntu-precise-daily-amd64-server-20130117) ** Attachment added: user-data showing and collecting output https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+attachment/3486284/+files/lp-1100491.txt -- 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: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100491] Re: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression]
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 13:57 ubuntu-server-ec2-testing-dev-testing-precise.list == grep Traceback /var/log/cloud-init.log == == apt-cache policy smhello == smello: Installed: (none) Candidate: 0.3~ppa1 Version table: 0.3~ppa1 0 500 http://ppa.launchpad.net/ubuntu-server-ec2-testing-dev/testing/ubuntu/ precise/main amd64 Packages == removing proposed list == == Done == I just did that test in: us-east-1 ami-d375feba canonical ebs/ubuntu-precise-daily-amd64-server-20130117.1 So the only precise / 12.04 images affected by this bug are the daily builds of 20130117. (fixed in 20130117.1 and later) -- 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: [SRU] apt_sources broken in 0.6.3-0ubuntu1.3 [regression] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1100491/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1090482] Re: over-riding distro config still broken
** 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 still broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1090482/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
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 notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
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) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Quantal) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu Precise) Status: New = Triaged ** Changed in: cloud-init (Ubuntu Quantal) Status: New = Triaged ** Changed in: cloud-init (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu Quantal) Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu Precise) Assignee: (unassigned) = Scott Moser (smoser) ** Changed in: cloud-init (Ubuntu Quantal) Assignee: (unassigned) = Scott Moser (smoser) -- 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/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-image-access] Easy machine access to Ubuntu image and cloud data
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 for mirroring data: DONE
+ add hooks to client for {new,remove} items: INPROGRESS
develop example hooks for populating ec2: TODO
document data format: TODO
--
Easy machine access to Ubuntu image and cloud data
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-image-access
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
** 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, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named ; ; connection timed out; no servers could be reached
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 filesystem (LP: #1050487) * support files written by klibc ipconfig to be found in /tmp or /run. copy files in /tmp to /run (LP: #1047722) To fix this, I have uploaded open-iscsi at version 2.0.871-0ubuntu9.12.04.2~maasppa0 to the maas ephemeral ppa (https://launchpad.net/~maas-maintainers/+archive/maas-ephemeral-images) The *real* fix is to get these two changes SRU'd. -- 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 be named ;; connection timed out; no servers could be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100920] Re: In Ubuntu 12.10, the legacy 'user' cloud-config option is not handled properly
** 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 is not handled properly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1101821] Re: mcollective fail
** 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: New ** Changed in: cloud-init (Ubuntu Precise) Status: New = Confirmed ** Changed in: cloud-init (Ubuntu Precise) Importance: Undecided = Low ** Changed in: cloud-init Importance: Undecided = Medium ** Changed in: cloud-init (Ubuntu) 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/1101821 Title: mcollective fail To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1101821/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100920] Re: In Ubuntu 12.10, the legacy 'user' cloud-config option is not handled properly
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 suggested is that the distro class in quantal returned a dict for 'get_default_user' the same as trunk does. The difference is one just comes from code (quantal) and the other from config (raring/trunk). b ** Patch added: debdiff for quantal https://bugs.launchpad.net/ubuntu/quantal/+source/cloud-init/+bug/1100920/+attachment/3509037/+files/lp-1100920-quantal-sru.patch -- 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 is not handled properly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100920] Re: In Ubuntu 12.10, the legacy 'user' cloud-config option is not handled properly
** 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 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 is not handled properly To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100920/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
** 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 / extracted afterwards. + == 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 + correctly implements locating this drive as it is present in OpenStack + in the folsom release. + + A change is being made in grizzly to allow for the device that contains + the data to be presented as a CD-ROM rather than a block device as it was + done in folsom. This changes is primarily driven by non-linux + hypervisors. + + In order to support Ubuntu cloud images running as a guest on grizzly + hypervisors that choose to attach the config-drive as a CD-ROM, we need + to make a change to cloud-init to consider CD-ROMs as a possible source. + Previously, cloud-init would ignore any device that ended with a digit + (0-9). Now, it allows the data to come from any block device that is + not a partition. + + [Test Case] + Attached to this bug is an ISO that provides config-drive-v2 data. + The following is the current situation: + attached-as-cdrom: cloud-init ignores. + attached-as-disk: cloud-init processes + + After the fix is applied, you will see; + attached-as-cdrom: cloud-init processes + attached-as-disk: cloud-init processes + + The provided ISO file simply sets a password for the 'ubuntu' user to + 'passw0rd'. So, verification that the test worked is as easy as logging + in with 'ubuntu' and 'passw0rd', either via ssh or via the console. + + To perform this test, download a quantal cloud-image from + http://cloud-images.ubuntu.com and boot it with kvm. + + Booting a kvm instance with iso as cdrom: + kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso + Booting a kvm instance with iso as disk: + kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso + + [Regression Potential] + The potential for regression is low. The most likely possibility for + error would be in incorrectly identifying a cd-rom and its content as a + config-drive. + == End SRU Information == + + + 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 / extracted afterwards. It should be optionally possible to access the ConfigDrive as a plain CDROM as well to simplify the access on any operating system. The raw HDD option compared to the CDROM one offers slightly better data access protection especially for the admin_pass field, but as this is going to be a deprecated option in the short term, the benefits are very limited compared to the additional complications for accessing the ConfigDrive data. -- 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/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1045955] Re: lxc-create -t ubuntu-cloud broken on quantal images (no ubuntu user)
** 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. https://bugs.launchpad.net/bugs/1045955 Title: lxc-create -t ubuntu-cloud broken on quantal images (no ubuntu user) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1045955/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1045955] Re: lxc-create -t ubuntu-cloud broken on quantal images (no ubuntu user)
** 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 quantal images (no ubuntu user) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1045955/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 961142] Re: chef 0.10: package installation: returned 100, expected 0
** 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 To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/961142/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037567] Re: need config-drive-v2 support
** 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. https://bugs.launchpad.net/bugs/1037567 Title: need config-drive-v2 support To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1037567/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1031065] Re: cloud-init-nonet runs 'start networking' explicitly
** 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 possible because of improvements + that have been made in mountall (bug 643289) and have been brought + back to 12.04. + + calling 'start networking' from cloud-init-nonet could cause issues + because other upstart 'start on' conditions might not be met at this + point in boot. + + The fix here is the same as is now applied in quantal and raring. + It more correctly addresses the root issue, that network-device-added + events were not being emitted in a container. There is now a job named + cloud-init-container that will emit 'network-device-added' events if + it is inside a container *and* its sanity checks show that the given + device has not already been brought up. + + [Test Case] + You can demonstrate why this change was necessary, and that the + provided change fixes the issue by doing the following: + + ## create a 'source' (pristine) root ## + sudo lxc-create -t ubuntu-cloud --name source-precise-amd64 -- \ +--release precise --arch amd64 --stream daily + + # set up 2 copies of the pristine root + # * 'nostart' just has cloud-init's call to 'start-networking' disabled + # * 'patched' contains the full upgraded cloud-init + sudo lxc-clone -o source-precise-amd64 -n nostart + f=/var/lib/lxc/nostart/etc/init/cloud-init-nonet.conf + if [ ! -e $f.dist ]; then +# disable 'start networking' in the cloud-init-nonet job +sudo cp $f $f.dist +sudo sed -i 's,^\([ ]\+start networking.*\),#\1,' $f + fi + + sudo lxc-clone -o source-precise-amd64 -n patched + deb=cloud-init_0.6.3-0ubuntu1.5~ppa1_all.deb + rpath=/var/lib/lxc/patched/rootfs + sudo cp $deb /var/lib/lxc/patched/rootfs/tmp + sudo LANG=C chroot /var/lib/lxc/patched/rootfs dpkg -i /tmp/$deb + + ## Now, start both. the 'nostart' root will hang on + ## cloud-init waiting for networking to come up. + ## the 'patched' will come all the way up quickly. + ## You can stop them with 'sudo lxc-stop -n name' + sudo lxc-start -n patched -- /sbin/init --verbose + sudo lxc-start -n nostart -- /sbin/init --verbose + + [Regression Potential] + Regressions would be likely to occur in one of 2 places: + a.) inside a container, where cloud-init-container caused a + problem by emitting its network-device-added events + + Here, the problem would be very limited to lxc containers + that have cloud-init inside them. This is likely very small. + + b.) outside a container, where 'start networking' was previously + fixing a boot deadlock that could have occurred. + Here, the changes are basically making precise work like 12.10 + and 13.04, so hopefully issues would have been shaken out there. + == End SRU Information == + + In development of 'overlayroot' package, I was mounting / as rw in the initramfs. This was causing a different order of execution of mounts, and as a result a different order of networking resolvconf and networking bringup. It exposed a bug in resolvconf, which was being called on boot in this order: Mon Jul 30 19:08:58 UTC 2012 /sbin/resolvconf -a lo.inet Mon Jul 30 19:08:59 UTC 2012 /sbin/dhclient-script Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.dhclient Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf -a eth0.inet Mon Jul 30 19:08:59 UTC 2012 /sbin/resolvconf --enable-updates Mon Jul 30 19:08:59 UTC 2012 /etc/resolvconf/update.d/libc -u The normal order is for resolvconf --enable-updates to be called (from /etc/init/resolvconf.conf) before anything else. As a result, I was seeing errors like: resolvconf: Error: /run/resolvconf/interface either does not exist or is not a directory This may be exposing a more grave issue, in that I believe the reason for dhclient coming up before resolvconf.conf started was that it was being run as a result of /etc/init/network-interface.conf. I don't immediately see how that is guarnateed to have /run ounted at all. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: resolvconf 1.67ubuntu1 ProcVersionSignature: User Name 3.5.0-6.6-generic 3.5.0 Uname: Linux 3.5.0-6-generic x86_64 Architecture: amd64 Date: Mon Jul 30 20:07:04 2012 PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: resolvconf UpgradeStatus: No upgrade log present (probably fresh install) Related Bugs: * bug 800824: cloud-init-nonet times out in lxc * bug 925122: container's udevadm trigger --add affects the host - * bug 643289: idmapd does not starts to work after system reboot + * bug 643289: idmapd does not starts to work after system reboot -- You received this bug
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
** 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. https://bugs.launchpad.net/bugs/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037567] Re: need config-drive-v2 support
** 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 + cloud platform) to the guest (instance). config-drive-v2 was implemented + in Openstack Folsom release, and delivered as functional in 12.10 Ubuntu. + In order to support Ubuntu 12.04 cloud images running as a guest on + Openstack clouds that utilize config-drive, we need to backport this + function to 12.04. + + This feature backport can be considered hardware enablement as it + enables Ubuntu images to work on new cloud platforms. + + [Test Case] + Attached to this bug is an ISO that provides config-drive-v2 data. + Currently, if you attach the ISO to a cloud-image instance, + it will be ignored. + + The new version of cloud-init enables data to be read from the disk. + + The provided ISO file simply sets a password for the 'ubuntu' user to + 'ubuntu'. So, verification that the test worked is as easy as logging + in with 'ubuntu' and 'passw0rd', either via ssh or via the console. + Additionally, when the config-drive is not found, cloud-init will fall + back to the EC2 data source, and block boot for several minutes as it + waits. When the config-drive is found, boot will occur quickly. + + To perform this test, download a precise cloud-image from + http://cloud-images.ubuntu.com patch it, and boot it with kvm. + + $ imgurl=http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img; + $ deburl=wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb; + $ isourl=https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz; + + $ wget $url -O precise-amd64.img.dist + $ wget $deburl -O cloud-init.deb + $ wget $isourl -O cfgdisk.img.dist; + + $ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist + $ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist + + $ zcat --force cfgdisk.img.dist cfgdisk.img + $ chmod 600 cfgdisk.img disk1.img.dist + + # patch the patched.img.dist with new cloud-init + $ bzr branch lp:~smoser/+junk/backdoor-image ./bi + $ sudo ./bi/mount-callback-umount patched.img.dist -- \ + sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp + LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ; + rm $mp/tmp/cloud-init.deb' -- + + $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img + $ qemu-img create -f qcow2 -b patched.img.dist patched.img + + # boot patched and unpatched images + $ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio + $ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio + + The unpatched version will take quite a long time to boot, and you'll messages + on the serial console like:see: + 2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 + + Booting a kvm instance with iso as cdrom: + kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso + Booting a kvm instance with iso as disk: + kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso + + [Regression Potential] + The potential for regression is low. The most likely possibility for + error would be in incorrectly identifying a cd-rom and its content as a + config-drive. + == End SRU Information == + + + ## Howto launch instance with config-drive ### + nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey + nova boot --key_name=mykey --image=$IMAGE \ +--config-drive=1 --flavor=m1.tiny \ +--user_data=./user-data.txt cfg-drive-test + 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]. [1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2 [2] http://paste.ubuntu.com/1150619/ ** 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 order to support Ubuntu 12.04 cloud images running as a guest on Openstack clouds that utilize config-drive, we need to backport this function to 12.04. This feature backport can be considered hardware enablement as it enables Ubuntu images to work on new cloud platforms. [Test Case] Attached to this bug is an ISO that provides config-drive-v2 data. Currently, if you attach the ISO to a cloud-image instance, it will be ignored. The new version of cloud-init enables data to be read from the disk. The provided ISO file simply sets a password for the 'ubuntu' user to 'ubuntu'. So, verification that the test worked is as easy
[Bug 1037567] Re: need config-drive-v2 support
** 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 order to support Ubuntu 12.04 cloud images running as a guest on Openstack clouds that utilize config-drive, we need to backport this function to 12.04. This feature backport can be considered hardware enablement as it enables Ubuntu images to work on new cloud platforms. [Test Case] Attached to this bug is an ISO that provides config-drive-v2 data. Currently, if you attach the ISO to a cloud-image instance, it will be ignored. The new version of cloud-init enables data to be read from the disk. The provided ISO file simply sets a password for the 'ubuntu' user to 'ubuntu'. So, verification that the test worked is as easy as logging in with 'ubuntu' and 'passw0rd', either via ssh or via the console. Additionally, when the config-drive is not found, cloud-init will fall back to the EC2 data source, and block boot for several minutes as it waits. When the config-drive is found, boot will occur quickly. To perform this test, download a precise cloud-image from http://cloud-images.ubuntu.com patch it, and boot it with kvm. $ imgurl=http://cloud-images.ubuntu.com/releases/precise/release-20130124/ubuntu-12.04-server-cloudimg-amd64-disk1.img; - $ deburl=wget https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb; + $ deburl=https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.6.3-0ubuntu1.5%7Eppa1_all.deb; $ isourl=https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz; - $ wget $url -O precise-amd64.img.dist + $ wget $imgurl -O precise-amd64.img.dist $ wget $deburl -O cloud-init.deb $ wget $isourl -O cfgdisk.img.dist; $ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist $ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist $ zcat --force cfgdisk.img.dist cfgdisk.img $ chmod 600 cfgdisk.img disk1.img.dist # patch the patched.img.dist with new cloud-init $ bzr branch lp:~smoser/+junk/backdoor-image ./bi $ sudo ./bi/mount-callback-umount patched.img.dist -- \ sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ; rm $mp/tmp/cloud-init.deb' -- $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img $ qemu-img create -f qcow2 -b patched.img.dist patched.img # boot patched and unpatched images $ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio $ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio The unpatched version will take quite a long time to boot, and you'll messages on the serial console like:see: 2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 [Regression Potential] The potential for regression is low. The most likely possibility for error would be in incorrectly identifying a cd-rom and its content as a config-drive. == End SRU Information == ## Howto launch instance with config-drive ### nova keypair-add --pub-key ~/.ssh/id_rsa.pub mykey nova boot --key_name=mykey --image=$IMAGE \ --config-drive=1 --flavor=m1.tiny \ --user_data=./user-data.txt cfg-drive-test 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]. [1] https://blueprints.launchpad.net/nova/+spec/config-drive-v2 - [2] http://paste.ubuntu.com/1150619/ -- 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 config-drive-v2 support To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1037567/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
** 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 correctly implements locating this drive as it is present in OpenStack in the folsom release. A change is being made in grizzly to allow for the device that contains the data to be presented as a CD-ROM rather than a block device as it was - done in folsom. This changes is primarily driven by non-linux + done in folsom. This changes is primarily driven by non-linux hypervisors. In order to support Ubuntu cloud images running as a guest on grizzly hypervisors that choose to attach the config-drive as a CD-ROM, we need to make a change to cloud-init to consider CD-ROMs as a possible source. Previously, cloud-init would ignore any device that ended with a digit - (0-9). Now, it allows the data to come from any block device that is + (0-9). Now, it allows the data to come from any block device that is not a partition. [Test Case] Attached to this bug is an ISO that provides config-drive-v2 data. The following is the current situation: attached-as-cdrom: cloud-init ignores. attached-as-disk: cloud-init processes After the fix is applied, you will see; attached-as-cdrom: cloud-init processes attached-as-disk: cloud-init processes - The provided ISO file simply sets a password for the 'ubuntu' user to - 'passw0rd'. So, verification that the test worked is as easy as logging + The provided ISO file simply sets a password for the 'ubuntu' user to + 'passw0rd'. So, verification that the test worked is as easy as logging in with 'ubuntu' and 'passw0rd', either via ssh or via the console. - To perform this test, download a quantal cloud-image from + To perform this test, download a quantal cloud-image from http://cloud-images.ubuntu.com and boot it with kvm. - Booting a kvm instance with iso as cdrom: - kvm -drive disk1.img,if=virtio -cdrom lp-1077020.iso - Booting a kvm instance with iso as disk: - kvm -drive disk1.img,if=virtio -drive lp-1077020.iso,if=virtio lp-1077020.iso + $ imgurl=http://cloud-images.ubuntu.com/releases/quantal/release-20121218/ubuntu-12.10-server-cloudimg-amd64-disk1.img; + $ deburl=https://launchpad.net/~smoser/+archive/cloud-init-test/+files/cloud-init_0.7.0-0ubuntu2.3%7Eppa0_all.deb; + $ isourl=https://bugs.launchpad.net/cloud-init/+bug/1100545/+attachment/3509470/+files/disk.config.gz; + + $ wget $imgurl -O quantal-amd64.img.dist + $ wget $deburl -O cloud-init.deb + $ wget $isourl -O cfgdisk.img.dist; + + $ qemu-img convert -O qcow2 quantal-amd64.img.dist disk1.img.dist + $ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist + + $ zcat --force cfgdisk.img.dist cfgdisk.img + $ chmod 600 cfgdisk.img disk1.img.dist + + # patch the patched.img.dist with new cloud-init + $ bzr branch lp:~smoser/+junk/backdoor-image ./bi + $ sudo ./bi/mount-callback-umount patched.img.dist -- \ + sh -ec 'mp=$1; cp cloud-init.deb $mp/tmp + LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ; + rm $mp/tmp/cloud-init.deb' -- + + $ qemu-img create -f qcow2 -b patched.img.dist patched.img + + # boot patched and unpatched images as cdrom and as disk + ## unpatched-disk (works) + $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img + $ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio + + ## unpatched-cdrom (config-drive ignored, long boot, fail) + $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img + $ kvm -m 512 -drive file=unpatched.img,if=virtio -cdrom cfgdisk.img + + ## patched-disk (works) + $ qemu-img create -f qcow2 -b patched.img.dist patched.img + $ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio + + ## patched-cdrom (FIXED) + $ qemu-img create -f qcow2 -b patched.img.dist patched.img + $ kvm -m 512 -drive file=patched.img,if=virtio -cdrom cfgdisk.img + + The unpatched version with cdrom will take quite a long time to boot, and + you'll messages on the serial console like:see: + 2013-01-31 18:53:18,185 - DataSourceEc2.py[CRITICAL]: giving up on md after 120 [Regression Potential] - The potential for regression is low. The most likely possibility for + The potential for regression is low. The most likely possibility for error would be in incorrectly identifying a cd-rom and its content as a config-drive. - == End SRU Information == + == End SRU Information == - 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 / extracted afterwards. + Currently Cloud-Init requires the ConfigDrive to be available
[Bug 1081660] Re: If maas-enlist fails to reach a DNS server, the node will be named ; ; connection timed out; no servers could be reached
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 maas-enlist fails to reach a DNS server, the node will be named ;; connection timed out; no servers could be reached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas-enlist/+bug/1081660/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
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 \ /etc/apt/sources.list.d/$rel-proposed.list apt-get update -q -y apt-get install cloud-init -q -y' ** 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/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1016695] Re: add console=tty1 to cloud-image kernel boot parameters
** 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 I manually add console=tty0 first. Can you add console=tty0 after console=ttyS0 so boot process will display automatically? I would really appreciate it. + + Related bugs: + bug 1122245: booting from a cloud image hangs until virsh console is used -- 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 kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
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. https://bugs.launchpad.net/bugs/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1029430] Re: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded
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 on the same host as compute adam_g smoser: devstack that just happens to be the case, but its not multihost adam_g smoser: anyway, the workaround is to jus rmmod vhost_net or add the iptables mangle rule described in that bug So specifically for devstack: rmmod vhost_net or [ -e /dev/vhost-net ] sudo iptables -t mangle -A POSTROUTING -o br100 -p udp -m udp --dport 68 -j CHECKSUM --checksum-fill -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1029430 Title: KVM guests networking issues with no virbr0 and with vhost_net kernel modules loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1029430/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: cloud-init parses yaml incorrectly
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 dangerously late in the boot process, given that runcmd is happening via cloud-config.conf at start on (filesystem and started rsyslog) At what point in boot is it safe to put files in /tmp (even temporary files) and assume that they will not be deleted by 'mounted-tmp' ? ** Package changed: cloud-init (Ubuntu) = mountall (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/1124384 Title: cloud-init parses yaml incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
** 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 http://cloud-images.ubuntu.com/raring/ with an outdated version of upstart (e.g 2013.01.23 - I saved this image, if you need it and it is not available from the mirror just ask) 2. Prepare a cloud-config script with the directives (example cloud-config script used by lp:auto-package-testing attached): apt_update: true apt_upgrade: true 3. Initialize the cloud image with this cloud-config script EXPECTED RESULT: Installation finish ACTUAL RESULT The service cloud-final is never executed and the flag boot-finished is not present. cloud-init logs of a failed installation attached. + Related bugs: + * bug 1080841: should reload configuration if an upstart job is added + * bug 1124384: reload-configuration can confuse upstart + ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cloud-init (not installed) ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Uname: Linux 3.8.0-1-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Thu Jan 24 09:08:19 2013 MarkForUpload: True ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR=set - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: Upgraded to raring on 2012-01-31 (358 days ago) -- 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/1103881 Title: cloud-final is never executed if upstart is upgraded during initialization of the image To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1080841] Re: should reload configuration if an upstart job is added
** 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 done by: - initctl reload-configuration + initctl reload-configuration + + Related bugs: + * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image + * bug 1124384: 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/1080841 Title: should reload configuration if an upstart job is added To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1080841/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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 wrote a upstart job. This was necessary because + inotify is not supported on all filesystems (overlayfs being the one of + most current interst). - Cloud-init is parsing YAML incorrectly - runcmd: - ... - [ sh, -c, echo = $(date) ': hello world!' = ] - ... - [ sh, -c, 'echo $(date) /root/runcmd.date.txt' ] - ... - [ wget, http://slashdot.org;, -O, /tmp/index.html ] - ... - touch /tmp/done + This seems to be causing upstart some pain, and resulting in cloud-final + (and 'rc') not being run. - Fails, while changing - touch /tmp/done to - [ touch /tmp/done ] - works. + Easy user-data to reproduce the problem is: + + #cloud-config-archive + - content: | +#!/bin/sh +echo $(date -R): user-script run === | tee /run/user-script.log + - content: | +#upstart-job +description a test upstart job +start on stopped rc RUNLEVEL=[2345] +console output +task +script +echo $(date -R): upstart job run === | tee /run/upstart-job.log +end script + + You should (and do on quantal) end up with 2 files written to /run. + + I've verified that the same behavior is true on quantal. If you change + cloud-init to notify upstart about a job immediately after it writes it, + then quantal's upstart gets confused also. + + Related bugs: + * bug 1080841: should reload configuration if an upstart job is added + * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image ** Also affects: upstart (Ubuntu) Importance: Undecided Status: New -- 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: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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) Status: New = Confirmed ** Changed in: upstart (Ubuntu) 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/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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 cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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 is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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 Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image
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: |
#upstart-job
description a test upstart job
start on stopped rc RUNLEVEL=[2345]
console output
task
script
echo $(date -R): upstart job run === | tee /run/upstart-job.log
end script
- content: |
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
Then:
sudo apt-get install kvm cloud-utils genisoimage
wget
http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd64-disk1.img
-O disk.img.dist
qemu-img convert -O qcow2 disk.img.dist disk.img.orig
qemu-img create -f qcow2 -b disk.img.orig disk.img
cloud-localds my-seed.img my-user-data
kvm -net nic -net user,hostfwd=tcp::-:22 \
-hda disk.img -hdb my-seed.img -m 512
Due to the fact that the bug blocks gettys from running, you'll have to ssh in.
Thats why i've done the host forwarding there.
You'll be able to log in with 'ubuntu' and 'passw0rd'. Remember that console
output will be going to the serial device.
--
[1]
http://ubuntu-smoser.blogspot.com/2013/02/using-ubuntu-cloud-images-without-cloud.html
--
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/1103881
Title:
cloud-final is never executed if upstart is upgraded during
initialization of the image
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
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 is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1124384 Title: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 43574] Re: Needs Ubuntu-style init script
** 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 notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/43574/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** 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 grub2 style
configuration (/boot/grub/grub.cfg). Thus, we have installed inside
cloud-images, a package named 'grub-legacy-ec2' that maintains
/boot/grub/menu.lst.
+
+ grub-legacy-ec2 does not simply assume all kernels are candidates for
+ inclusion in /boot/grub/menu.lst. Instead, it has some very basic
+ whitelist metrics. Those previously required a kernel to end in
+ '-virtual'.
+
+ In the development cycle of 12.10, the -virtual kernel went away. It is
+ now simply a -generic kernel with a subset of modules.
+
+ [Impact]
+ In 12.04, it is now supported to run a 12.10 backports kernel. These new
kernels will be named in the newer fashion, and will end in '-generic', rather
than '-virtual'. As a result, grub-legacy-ec2's whitelist will not write
entries for these kernels to /boot/grub/menu.lst.
+
+ The end result is that the user who installs these kernels will not be
+ able to easily boot them on EC2 (or other xen guest).
+
+ [Test Case]
+ * Boot a cloud instance or cloud image
+ * install a backports kernel
+ * verify that kernel new kernel is included in /boot/grub/menu.lst
+Previously the kernel would not be included there.
+
+ [Regression Potential]
+ The biggest potential for regression would be in writing an entry to
/boot/grub/menu.lst for a kernel that would not boot. There is protection
against this in the included patch by checking the version number as well as
the name.
+
+ That amounts to:
+ dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 return 0;;
+ where 'ver_flavor' is the version as found in the file name of the kernel
(ie, /boot/vmlinux-2.6.35-13-generic).
+ == End SRU Information ==
+
Quantal stopped booting on EC2 around 2012-05-25.
ben@padfoot:~$ ec2-get-console-output -i i-75727213
Required parameter 'INSTANCE' missing (-h for usage)
ben@padfoot:~$ ec2-get-console-output i-75727213
i-75727213
2012-05-28T14:17:49+
Xen Minimal OS!
- start_info: 0xb1(VA)
- nr_pages: 0x6a400
- shared_inf: 0x001a5000(MA)
- pt_base: 0xb13000(VA)
+ start_info: 0xb1(VA)
+ nr_pages: 0x6a400
+ shared_inf: 0x001a5000(MA)
+ pt_base: 0xb13000(VA)
nr_pt_frames: 0x9
- mfn_list: 0x967000(VA)
-mod_start: 0x0(VA)
- mod_len: 0
-flags: 0x0
- cmd_line: root=/dev/sda1 ro 4
- stack: 0x946780-0x966780
+ mfn_list: 0x967000(VA)
+ mod_start: 0x0(VA)
+ mod_len: 0
+ flags: 0x0
+ cmd_line: root=/dev/sda1 ro 4
+ stack: 0x946780-0x966780
MM: Init
- _text: 0x0(VA)
- _etext: 0x61e65(VA)
-_erodata: 0x76000(VA)
- _edata: 0x7b6d4(VA)
+ _text: 0x0(VA)
+ _etext: 0x61e65(VA)
+ _erodata: 0x76000(VA)
+ _edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
-_end: 0x966d34(VA)
- start_pfn: b1f
- max_pfn: 6a400
+ _end: 0x966d34(VA)
+ start_pfn: b1f
+ max_pfn: 6a400
Mapping memory range 0xc0 - 0x6a40
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for e6c000(e6c000)-0(6a40)
MM: done
Demand map pfns at 6a401000-7a401000.
Heap resides at 7a402000-ba402000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6a401000.
Initialising scheduler
Thread Idle: pointer: 0x7a402008, stack: 0x6a03
Initialising xenbus
Thread xenstore: pointer: 0x7a402478, stack: 0x6a04
Dummy main: start_info=0x966880
Thread main: pointer: 0x7a4028e8, stack: 0x6a05
- main root=/dev/sda1 ro 4
+ main root=/dev/sda1 ro 4
vbd 2049 is hd0
*** BLKFRONT for device/vbd/2049 **
-
backend at /local/domain/0/backend/vbd/126/2049
Failed to read /local/domain/0/backend/vbd/126/2049/feature-barrier.
Failed to read /local/domain/0/backend/vbd/126/2049/feature-flush-cache.
16777216 sectors of 0 bytes
**
vbd 2050 is hd1
*** BLKFRONT for device/vbd/2050 **
-
backend at /local/domain/0/backend/vbd/126/2050
Failed to read /local/domain/0/backend/vbd/126/2050/feature-barrier.
Failed to read /local/domain/0/backend/vbd/126/2050/feature-flush-cache.
312705024 sectors of 0 bytes
**
vbd 2051 is hd2
*** BLKFRONT for device/vbd/2051 **
-
backend at /local/domain/0/backend/vbd/126/2051
Failed to read /local/domain/0/backend/vbd/126/2051/feature-barrier.
Failed to read /local/domain/0/backend/vbd/126/2051/feature-flush-cache.
1835008 sectors of 0 bytes
**
[H[J Booting 'Ubuntu quantal (development branch), memtest86+'
root (hd0)
- Filesystem type is ext2fs, using whole
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
** 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 grub2 style
configuration (/boot/grub/grub.cfg). Thus, we have installed inside
cloud-images, a package named 'grub-legacy-ec2' that maintains
/boot/grub/menu.lst.
grub-legacy-ec2 does not simply assume all kernels are candidates for
inclusion in /boot/grub/menu.lst. Instead, it has some very basic
whitelist metrics. Those previously required a kernel to end in
'-virtual'.
In the development cycle of 12.10, the -virtual kernel went away. It is
now simply a -generic kernel with a subset of modules.
[Impact]
- In 12.04, it is now supported to run a 12.10 backports kernel. These new
kernels will be named in the newer fashion, and will end in '-generic', rather
than '-virtual'. As a result, grub-legacy-ec2's whitelist will not write
entries for these kernels to /boot/grub/menu.lst.
+ In 12.04, it is now supported to run a 12.10 enablement kernel
(https://wiki.ubuntu.com/Kernel/LTSEnablementStack). These new kernels will be
named in the newer fashion, and will end in '-generic', rather than '-virtual'.
As a result, grub-legacy-ec2's whitelist will not write entries for these
kernels to /boot/grub/menu.lst.
The end result is that the user who installs these kernels will not be
able to easily boot them on EC2 (or other xen guest).
[Test Case]
- * Boot a cloud instance or cloud image
- * install a backports kernel
- * verify that kernel new kernel is included in /boot/grub/menu.lst
-Previously the kernel would not be included there.
+ * Boot a cloud instance or cloud image
+The daily build of a EC2 AMI id at
http://cloud-images.ubuntu.com/server/precise/current/ is fine.
+ * install a backports kernel
+sudo apt-get install linux-generic-lts-quantal
+ * verify that kernel new kernel is included in /boot/grub/menu.lst
+ Previously the kernel would not be included there.
+Previously:
+$ grep 3.5.[0-9] /boot/grub/menu.lst || echo NOT_FOUND
+NOT_FOUND
+
+But with new update-grub, it will be.
+# enable proposed
+$ echo deb http://archive.ubuntu.com/ubuntu precise-proposed main |
+ sudo tee /etc/apt/sources.list.d/proposed.list
+$ sudo apt-get update
+$ sudo apt-get install grub-legacy-ec2
+$ sudo update-grub-legacy-ec2
+$ grep 3.5.[0-9] /boot/grub/menu.lst || echo NOT_FOUND
+titleUbuntu 12.04.2 LTS, kernel 3.5.0-24-generic
+kernel /boot/vmlinuz-3.5.0-24-generic root=LABEL=cloudimg-rootfs ro
console=hvc0
+...
[Regression Potential]
The biggest potential for regression would be in writing an entry to
/boot/grub/menu.lst for a kernel that would not boot. There is protection
against this in the included patch by checking the version number as well as
the name.
That amounts to:
- dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 return 0;;
+ dpkg --compare-versions ${ver_flavor%-generic} ge 3.4.0-3 return 0;;
where 'ver_flavor' is the version as found in the file name of the kernel
(ie, /boot/vmlinux-2.6.35-13-generic).
== End SRU Information ==
Quantal stopped booting on EC2 around 2012-05-25.
ben@padfoot:~$ ec2-get-console-output -i i-75727213
Required parameter 'INSTANCE' missing (-h for usage)
ben@padfoot:~$ ec2-get-console-output i-75727213
i-75727213
2012-05-28T14:17:49+
Xen Minimal OS!
start_info: 0xb1(VA)
nr_pages: 0x6a400
shared_inf: 0x001a5000(MA)
pt_base: 0xb13000(VA)
nr_pt_frames: 0x9
mfn_list: 0x967000(VA)
mod_start: 0x0(VA)
mod_len: 0
flags: 0x0
cmd_line: root=/dev/sda1 ro 4
stack: 0x946780-0x966780
MM: Init
_text: 0x0(VA)
_etext: 0x61e65(VA)
_erodata: 0x76000(VA)
_edata: 0x7b6d4(VA)
stack start: 0x946780(VA)
_end: 0x966d34(VA)
start_pfn: b1f
max_pfn: 6a400
Mapping memory range 0xc0 - 0x6a40
setting 0x0-0x76000 readonly
skipped 0x1000
MM: Initialise page allocator for e6c000(e6c000)-0(6a40)
MM: done
Demand map pfns at 6a401000-7a401000.
Heap resides at 7a402000-ba402000.
Initialising timer interface
Initialising console ... done.
gnttab_table mapped at 0x6a401000.
Initialising scheduler
Thread Idle: pointer: 0x7a402008, stack: 0x6a03
Initialising xenbus
Thread xenstore: pointer: 0x7a402478, stack: 0x6a04
Dummy main: start_info=0x966880
Thread main: pointer: 0x7a4028e8, stack: 0x6a05
main root=/dev/sda1 ro 4
vbd 2049 is hd0
*** BLKFRONT for device/vbd/2049 **
backend at /local/domain/0/backend/vbd/126/2049
Failed to read /local/domain/0/backend/vbd/126/2049/feature-barrier.
Failed to read
[Bug 1031065] Re: cloud-init-nonet runs 'start networking' explicitly
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: server serial: 20130218 $ sudo lxc-clone -o source-precise-amd64 -n patched $ url=https://launchpad.net/ubuntu/+source/cloud-init/0.6.3-0ubuntu1.5/+build/4312778/+files/cloud-init_0.6.3-0ubuntu1.5_all.deb; $ deb=cloud-init_0.6.3-0ubuntu1.5_all.deb $ wget -O $deb $url $ sudo cp $deb /var/lib/lxc/patched/rootfs/tmp $ sudo LANG=C chroot /var/lib/lxc/patched/rootfs dpkg -i /tmp/$deb $ sudo lxc-start -n patched -- /sbin/init --verbose Verify can log in as ubuntu/ubuntu. ** 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/1031065 Title: cloud-init-nonet runs 'start networking' explicitly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1031065/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1005551] Re: update-grub-legacy-ec2 ignores kernels named -generic
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 apt-get install linux-generic-lts-quantal -y -q $ grep 3.5.[0-9] /boot/grub/menu.lst || echo NOT_FOUND NOT_FOUND $ ls /boot/vmlinuz-3.* /boot/vmlinuz-3.2.0-37-virtual /boot/vmlinuz-3.5.0-23-generic $ echo deb http://archive.ubuntu.com/ubuntu precise-proposed main | sudo tee /etc/apt/sources.list.d/proposed.list $ sudo apt-get update $ sudo apt-get install grub-legacy-ec2 $ dpkg-query --show grub-legacy-ec2 grub-legacy-ec2 0.6.3-0ubuntu1.5 $ grep ^title.*3.5.[0-9] /boot/grub/menu.lst || echo NOT_FOUND titleUbuntu 12.04.2 LTS, kernel 3.5.0-23-generic titleUbuntu 12.04.2 LTS, kernel 3.5.0-23-generic (recovery mode) ** 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/1005551 Title: update-grub-legacy-ec2 ignores kernels named -generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1005551/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1037567] Re: need config-drive-v2 support
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; $ deburl=https://launchpad.net/ubuntu/+source/cloud-init/0.6.3-0ubuntu1.5/+build/4312778/+files/cloud-init_0.6.3-0ubuntu1.5_all.deb; $ isourl=https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz; $ wget $imgurl -O precise-amd64.img.dist $ wget $deburl -O cloud-init.deb $ wget $isourl -O cfgdisk.img.dist; $ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist $ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist $ zcat --force cfgdisk.img.dist cfgdisk.img $ chmod 600 cfgdisk.img disk1.img.dist ## patch the patched.img.dist with new cloud-init $ bzr branch lp:~smoser/+junk/backdoor-image ./bi $ sudo ./bi/mount-callback-umount patched.img.dist -- \ sh -ec 'mp=$MOUNTPOINT; cp cloud-init.deb $mp/tmp LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ; rm $mp/tmp/cloud-init.deb' -- $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img $ qemu-img create -f qcow2 -b patched.img.dist patched.img # boot patched and unpatched images $ kvm -m 512 -drive file=unpatched.img,if=virtio -drive file=cfgdisk.img,if=virtio $ kvm -m 512 -drive file=patched.img,if=virtio -drive file=cfgdisk.img,if=virtio ** 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/1037567 Title: need config-drive-v2 support To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1037567/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1100545] Re: It should be possible to access the ConfigDrive as a CDROM drive as well
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; $ deburl=https://launchpad.net/ubuntu/+source/cloud-init/0.6.3-0ubuntu1.5/+build/4312778/+files/cloud-init_0.6.3-0ubuntu1.5_all.deb; $ isourl=https://bugs.launchpad.net/cloud-init/+bug/1037567/+attachment/3509468/+files/disk.config.gz; $ wget $imgurl -O precise-amd64.img.dist $ wget $deburl -O cloud-init.deb $ wget $isourl -O cfgdisk.img.dist; $ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist $ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist $ zcat --force cfgdisk.img.dist cfgdisk.img $ chmod 600 cfgdisk.img disk1.img.dist ## patch the patched.img.dist with new cloud-init $ bzr branch lp:~smoser/+junk/backdoor-image ./bi $ sudo ./bi/mount-callback-umount patched.img.dist -- \ sh -ec 'mp=$MOUNTPOINT; cp cloud-init.deb $mp/tmp LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ; rm $mp/tmp/cloud-init.deb' -- $ qemu-img create -f qcow2 -b disk1.img.dist unpatched.img $ qemu-img create -f qcow2 -b patched.img.dist patched.img # boot patched and unpatched images $ kvm -m 512 -drive file=patched.img,if=virtio -cdrom cfgdisk.img -curses % grep found.data.source /var/log/cloud-init.log 2013-02-19 21:50:40,887 - __init__.py[DEBUG]: found data source DataSourceConfigDriveNet 2013-02-19 21:50:40,957 - cloud-init[DEBUG]: found data source: DataSourceConfigDrive [net,ver=2][source=/dev/sr0] ** 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/1100545 Title: It should be possible to access the ConfigDrive as a CDROM drive as well To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1100545/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1077020] Re: cloud-init ca-certs leaves a blank line in /etc/ca-certificates.conf
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
$
imgurl=http://cloud-images.ubuntu.com/releases/precise/release-20130204/ubuntu-12.04-server-cloudimg-amd64-disk1.img;
$
deburl=https://launchpad.net/ubuntu/+source/cloud-init/0.6.3-0ubuntu1.5/+build/4312778/+files/cloud-init_0.6.3-0ubuntu1.5_all.deb;
$ wget $imgurl -O precise-amd64.img.dist
$ wget $deburl -O cloud-init.deb
$ qemu-img convert -O qcow2 precise-amd64.img.dist disk1.img.dist
$ qemu-img create -f qcow2 -b disk1.img.dist patched.img.dist
## patch the patched.img.dist with new cloud-init
$ sudo ./bi/mount-callback-umount patched.img.dist -- \
sh -ec 'mp=$MOUNTPOINT; cp cloud-init.deb $mp/tmp
LANG=C chroot $mp dpkg -i /tmp/cloud-init.deb ;
rm $mp/tmp/cloud-init.deb' --
$ qemu-img create -f qcow2 -b patched.img.dist patched.img
$ cat my-user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
output: {all: '| tee -a /var/log/cloud-init-output.log'}
ca-certs:
... ### content from above example 99-local-certs.cfg ###
$ echo instance-id: $(uuidgen || echo i-abcdefg) my-meta-data
$ cloud-localds my-seed.img my-user-data my-meta-data
$ kvm -m 512 -drive file=patched.img,if=virtio -cdrom my-seed.img
-curses
## now, logged in as ubuntu:passw0rd
% grep cloud-init.*found.data.source /var/log/cloud-init.log
found data source: DataSourceNoCloud [seed=/dev/sr0]
% grep -i cert /var/log/cloud-init-output.log
Updating certificates in /etc/ssl/certs... 1 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.ddone.
% ls -l /usr/lib/ssl/certs/ | grep -i cloud
lrwxrwxrwx 1 root root 23 Feb 19 22:04 b1d2b355.0 -
cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 23 Feb 19 22:04 cbbf81bb.0 - cloud-init-ca-certs.pem
lrwxrwxrwx 1 root root 50 Feb 19 22:04 cloud-init-ca-certs.pem -
/usr/share/ca-certificates/cloud-init-ca-certs.crt
** 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 /etc/ca-certificates.conf
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1077020/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1073077] Re: zsh complains about locale_warn on launch
** 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 bug go to: https://bugs.launchpad.net/cloud-init/+bug/1073077/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1016695] Re: add console=tty1 to cloud-image kernel boot parameters
** 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 kernel boot parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1016695/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1085537] Re: /etc/ssl/certs/cert-ec2.pem is dangling symlink
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 lrwxrwxrwx 1 root root 33 Jul 13 2012 /etc/ssl/certs/cert-ec2.pem - /usr/share/euca2ools/cert-ec2.pem $ ls -l /usr/share/euca2ools/cert-ec2.pem ls: cannot access /usr/share/euca2ools/cert-ec2.pem: No such file or directory # enable proposed $ echo deb http://archive.ubuntu.com/ubuntu $(lsb_release -sc)-proposed main | sudo tee /etc/apt/sources.list.d/proposed.list $ sudo apt-get update $ sudo apt-get install euca2ools $ dpkg-query --show euca2ools euca2ools 2.0.2-1ubuntu2.1 $ dpkg -L euca2ools | grep cert-ec2 /usr/share/euca2ools/cert-ec2.pem /etc/ssl/certs/cert-ec2.pem $ ls -l /etc/ssl/certs/cert-ec2.pem lrwxrwxrwx 1 root root 33 Jan 24 07:45 /etc/ssl/certs/cert-ec2.pem - /usr/share/euca2ools/cert-ec2.pem $ ls -l /usr/share/euca2ools/cert-ec2.pem -rw-r--r-- 1 root root 1379 Jun 13 2012 /usr/share/euca2ools/cert-ec2.pem $ head -n 3 /usr/share/euca2ools/cert-ec2.pem -BEGIN CERTIFICATE- MIIDzjCCAzegAwIBAgIJALDnZV+lpZdSMA0GCSqGSIb3DQEBBQUAMIGhMQswCQYD VQQGEwJaQTEVMBMGA1UECBMMV2VzdGVybiBDYXBlMRIwEAYDVQQHEwlDYXBlIFRv So, the upgrade fixed the broken symlink and got the right file content in place. ** 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 euca2ools in Ubuntu. https://bugs.launchpad.net/bugs/1085537 Title: /etc/ssl/certs/cert-ec2.pem is dangling symlink To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/euca2ools/+bug/1085537/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1045955] Re: lxc-create -t ubuntu-cloud broken on quantal images (no ubuntu user)
$ 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: 0.7.5-3ubuntu67 0 500 http://archive.ubuntu.com/ubuntu/ precise-proposed/universe amd64 Packages 0.7.5-3ubuntu66 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise-updates/universe amd64 Packages 0.7.5-3ubuntu52 0 500 http://nova.clouds.archive.ubuntu.com/ubuntu/ precise/universe amd64 Packages $ sudo apt-get install -q -y lxc distro-info $ sudo lxc-create -t ubuntu-cloud -n quantal-i386-source -- --release=quantal --arch=i386 $ sudo lxc-clone -o quantal-i386-source -n quantal-i386 $ sudo lxc-start -n quantal-i386 Then logged in using 'ubuntu:ubuntu'. ** 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 lxc in Ubuntu. https://bugs.launchpad.net/bugs/1045955 Title: lxc-create -t ubuntu-cloud broken on quantal images (no ubuntu user) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1045955/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Blueprint servercloud-r-fastpath-install] fast server install for cloud-image like experience
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 choice in MAAS on default and per-node basis: TODO + Integrate ephemeral boot installer support into MAAS for fast path installer: DONE + Support installer choice in MAAS on default and per-node basis: DONE Support user-scripts partitioning scripts for installer: TODO Support simplistic raid in installer: TODO Support late-command in installer: TODO Support kexec into booted system in installer: TODO Document installer: TODO -- fast server install for cloud-image like experience https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-fastpath-install -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1132345] Re: grub 0.97 and 2.00 installed in VMs causes confusion
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 'grub-legacy-ec2' to manage /boot/grub/menu.lst. Ie, if you really think you need that file managed, that is one solution. The other solution is to use drop grub 0.97 ** Also affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Changed in: vm-builder (Ubuntu) Importance: Medium = Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/1132345 Title: grub 0.97 and 2.00 installed in VMs causes confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1132345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1124384] Re: reload-configuration can confuse upstart
** 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 upstart some pain, and resulting in cloud-final (and 'rc') not being run. Easy user-data to reproduce the problem is: #cloud-config-archive - content: | +#boothook #!/bin/sh -echo $(date -R): user-script run === | tee /run/user-script.log +touch /run/cloud-init-upstart-reload # hack, see trunk commit 783 - content: | -#upstart-job -description a test upstart job -start on stopped rc RUNLEVEL=[2345] -console output -task -script -echo $(date -R): upstart job run === | tee /run/upstart-job.log -end script + #!/bin/sh + echo $(date -R): user-script run === | tee /run/user-script.log + - content: | + #upstart-job + description a test upstart job + start on stopped rc RUNLEVEL=[2345] + console output + task + script + echo $(date -R): upstart job run === | tee /run/upstart-job.log + end script You should (and do on quantal) end up with 2 files written to /run. I've verified that the same behavior is true on quantal. If you change cloud-init to notify upstart about a job immediately after it writes it, then quantal's upstart gets confused also. Related bugs: - * bug 1080841: should reload configuration if an upstart job is added - * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image + * bug 1080841: should reload configuration if an upstart job is added + * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image ** 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 upstart some pain, and resulting in cloud-final (and 'rc') not being run. Easy user-data to reproduce the problem is: #cloud-config-archive - content: | -#boothook -#!/bin/sh -touch /run/cloud-init-upstart-reload # hack, see trunk commit 783 + #cloud-boothook + #!/bin/sh + touch /run/cloud-init-upstart-reload # hack, see trunk commit 783 - content: | #!/bin/sh echo $(date -R): user-script run === | tee /run/user-script.log - content: | #upstart-job description a test upstart job start on stopped rc RUNLEVEL=[2345] console output task script echo $(date -R): upstart job run === | tee /run/upstart-job.log end script You should (and do on quantal) end up with 2 files written to /run. I've verified that the same behavior is true on quantal. If you change cloud-init to notify upstart about a job immediately after it writes it, then quantal's upstart gets confused also. Related bugs: * bug 1080841: should reload configuration if an upstart job is added * bug 1103881: cloud-final is never executed if upstart is upgraded during initialization of the image -- 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: reload-configuration can confuse upstart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1124384/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 333860] Re: Command to track which version of EC2 are we running.
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 subscribed to cloud-utils in Ubuntu. https://bugs.launchpad.net/bugs/333860 Title: Command to track which version of EC2 are we running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-utils/+bug/333860/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1136936] [NEW] growpart and cloud-utils should support growning mounted filesystem
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 function into growpart and cloud-init instead. By doing so, we can actually make it able to be disabled from user-data, and not require ramdisk code. Links: * util-linux upstream: http://git.kernel.org/?p=utils/util-linux/util-linux.git;a=commitdiff;h=3b905b794e93609af7e42459d32b27e7c18ce02e * kernel upstream: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c83f6bf98dc1f1a194118b3830706cebbebda8c4 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: cloud-utils 0.26-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1 Uname: Linux 3.5.0-21-generic x86_64 ApportVersion: 2.8-0ubuntu4 Architecture: amd64 Date: Thu Feb 28 22:27:54 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2011-10-19 (498 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-utils UpgradeStatus: Upgraded to raring on 2013-01-07 (52 days ago) ** Affects: cloud-init Importance: Undecided Status: New ** Affects: cloud-utils Importance: Undecided Status: New ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Affects: cloud-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug raring running-unity ** Also affects: cloud-utils Importance: Undecided Status: New ** Also affects: cloud-init Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New -- 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 growning mounted filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1136936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1136936] Re: growpart and cloud-utils should support growing mounted filesystem
** 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. https://bugs.launchpad.net/bugs/1136936 Title: growpart and cloud-utils should support growing mounted filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1136936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1136936] Re: growpart and cloud-utils should support growing mounted filesystem
** 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 Title: growpart and cloud-utils should support growing mounted filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1136936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015223] Re: cloud-init-nonet main process killed by TERM signal
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: cloud-init-nonet main process (679) killed by TERM signal After this commit, you wont see that any more. I was confused as to whether or not it would fix it as it was unclear if the message was stating that upstart was *sending* a kill to the given process, or that that process had been killed by TERM. It appears to be the latter. Also, now we'll see something this on console output: cloud-init start-local running: Mon, 04 Mar 2013 19:32:27 +. up 3.02 seconds no instance data found in start-local cloud-init-nonet[3.95]: waiting 10 seconds for network device cloud-init-nonet[13.95]: waiting 120 seconds for network device cloud-init-nonet[22.00]: static networking is now up -- 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/1015223 Title: cloud-init-nonet main process killed by TERM signal To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1015223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1015223] Re: cloud-init-nonet main process killed by TERM signal
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 Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/1015223 Title: cloud-init-nonet main process killed by TERM signal To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1015223/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1145215] Re: cloud-init mangles sources.lists if mirror can't be found
--- 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 = {
-'ubuntu': {
-'primary': http://archive.ubuntu.com/ubuntu;,
-'security': http://security.ubuntu.com/ubuntu;
-}
+'primary': http://archive.ubuntu.com/ubuntu;,
+'security': http://security.ubuntu.com/ubuntu;
}
mirror = None
That looks like the fix, but I suspect that your /etc/cloud/cloud.cfg
has been locally modified as the packaged version should provide a
['system_info']['package_mirrors'] entry that would make the above code
irrelevant (which is why it doesn't fail elsewhere, i think).
--
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/1145215
Title:
cloud-init mangles sources.lists if mirror can't be found
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1145215/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1069570] Re: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think...
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 to if this solves their problem. To test this: * build the package or use the ppa to get the updated version of isc-dhcp * modify /etc/maas/dhcpd.conf to include 'ignore-client-uids true' To me, this seems like the correct solution, and a valid patch to isc- dchp. The only reason we haven't landed on this as the solution, is that isc is a very un-available upstream, and bringing this patch into ubuntu means carrying (and supporting) quite likely without upstream support. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1069570 Title: 1 MAC Address, two IPs - DNS is out of sync with DHCP leases databases, I think... To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1069570/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1136936] Re: growpart and cloud-utils should support growing mounted filesystem
** 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 growing mounted filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1136936/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
