Update jaunty, karmic, lucid and maverick to landscape-client 1.5.4
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Invalid
|
Undecided
|
Unassigned | ||
landscape-client (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jaunty |
Fix Released
|
Undecided
|
Unassigned | ||
Karmic |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Landscape Client 1.5.4 has been released. We would like to get these changes into Maverick, Lucid, Karmic and Jaunty.
As far as released version of Ubuntu are concerned, the required pieces of information for the needed SRU follow (as laid out in the "Procedure" section of https:/
=== Statement explaining the impact ===
This release sports both bug-fixes and new features and we would like to make sure all of our supported customers (even those on Jaunty, Karmic and Lucid) have access to these improvements. The notable ones are:
1) The Eucalyptus management plugin now reports the output of the 'euca-describe-
2) Check if the package directory exists before trying to check the package changer lock in the dbus-proxy. This fixes a bug when upgrading a dbus-landscape which never registered.
3) Allow an LDS server to bootstrap new cloud instances with its own CA, which is picked up by the client, written to a file on the instance, and used in subsequent exchanges with the server.
4) Skip loopback interface when reporting device info.
5) Disable landscape-sysinfo when load is more than 1.
For more details see Bug #599338, Bug #603514, Bug #605079, Bug #608314, and Bug #608278 (all mentioned in the debian/changelog of the proposed packages).
=== How the bug has been addressed ===
We have been following the development procedure laid out in https:/
=== Patches ===
The three branches for the new landscape-client jaunty, karmic and lucid source packages are attached to this bug, and were derived from
lp:ubuntu/jaunty-updates/landscape-client
lp:ubuntu/karmic-updates/landscape-client
lp:ubuntu/lucid-updates/landscape-client
respectively.
=== Detailed instructions how to reproduce the bug ===
N/A
=== Discussion ===
All the source packages have been subject to the QA process detailed in the LandscapeUpdates document linked above.
=== How the bug has been addressed ===
We have been following the development procedure laid out in https:/
The profile in question was a "broken" one, meaning one that got its associated package retired at some point (it was before we implemented the fix for not retiring profile packages). Everything seem to work when bumping the profile in question (that re-generates its associated package) or creating a new profile.