cloud-init doesn't cache data source info
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Fix Released
|
Medium
|
Scott Moser | ||
Lucid |
Fix Released
|
Medium
|
Scott Moser |
Bug Description
Binary package hint: cloud-init
cloud-init doesn't correctly cache data it crawls from the metadata service.
The result is each of the jobs ends up crawling the metadata service. That alone shouldn't be a terribly bad thing, but today I saw one of the requests hang. The metadata service probably isn't tested to be thread save. The result of this is that jobs will be delayed and or not run.
The exact problem I saw, was that cloud-config-misc was hung. When I looked at it with 'lsof -p 340', I saw the following:
cloud-ini 340 root 3u IPv4 7010 0t0 TCP domU-12-
ProblemType: Bug
Architecture: i386
Date: Wed Feb 24 21:50:11 2010
DistroRelease: Ubuntu 10.04
Package: cloud-init 0.5.7-0ubuntu2 [modified: usr/share/
PackageArchitec
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: cloud-init
Uname: Linux 2.6.32-302-ec2 i686
This bug was fixed in the package cloud-init - 0.5.8-0ubuntu1
---------------
cloud-init (0.5.8-0ubuntu1) lucid; urgency=low
* New upstream release. cloudinit- updates
* cache data from metadata service, LP: #527364
* fix format of cron entry in cron.d/
* package egg-info file
-- Scott Moser <email address hidden> Tue, 02 Mar 2010 15:48:04 -0500