yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1066115@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package cloud-init - 0.6.3-0ubuntu1.3

---------------
cloud-init (0.6.3-0ubuntu1.3) precise-proposed; urgency=low

  * debian/patches/lp-1070345-landscape-restart-after-change.patch,
    debian/patches/lp-1066115-landscape-install-fix-perms.patch:
    fix missing or incorrect imports (LP: #1070345, LP: #1066115).

cloud-init (0.6.3-0ubuntu1.2) precise-proposed; urgency=low

  * debian/patches/lp-978127-maas-oauth-fix-bad-clock.patch: fix usage of
    oauth in maas data source if local system has a bad clock (LP: #978127)
  * debian/cloud-init.preinst: fix bug where user data scripts re-ran on
    upgrade from 10.04 versions (LP: #1049146)
  * debian/patches/lp-974509-detect-dns-server-redirection.patch: detect dns
    server redirection and disable searching dns for a mirror named
    'ubuntu-mirror' (LP: #974509)
  * debian/patches/lp-1018554-shutdown-message-to-console.patch: write a
    message to the console on system shutdown. (LP: #1018554)
  * debian/patches/lp-1066115-landscape-install-fix-perms.patch: install
    landscape package if needed which will ensure proper permissions on config
    file (LP: #1066115).
  * debian/patches/lp-1070345-landscape-restart-after-change.patch: restart
    landscape after modifying config (LP: #1070345)
  * debian/patches/lp-1073077-zsh-workaround-for-locale_warn.patch: avoid
    warning when user's shell is zsh (LP: #1073077)
  * debian/patches/rework-mirror-selection.patch: improve mirror selection by:
    * allowing region/availability-zone to be part of mirror (LP: #1037727)
    * making mirror selection arch aware (LP: #1028501)
    * allow specification of a security mirror (LP: #1006963)
 -- Scott Moser <smoser@xxxxxxxxxx>   Thu, 13 Dec 2012 12:16:56 -0500

** Changed in: cloud-init (Ubuntu Precise)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1066115

Title:
  The landscape client plugin doesn't create the config file with the
  proper permissions

Status in Init scripts for use on cloud images:
  Fix Released
Status in “cloud-init” package in Ubuntu:
  Fix Released
Status in “cloud-init” source package in Precise:
  Fix Released
Status in “cloud-init” source package in Quantal:
  Fix Released

Bug description:
  === Begin SRU Information ===
  [Impact]
   * If an image does not have landscape-client installed inside it, and the
     user provided landscape config, then:
     a.) the landscape config file would be written with root:root permissions
         so that the user that landscape runs as could not change it.
     b.) the landscape package would not be installed.

   * The fix here is just to install the landscape-client package.  This is
     clearly what the user would want.
     Additionally, no package installation occurs unless the user made that
     request.  The fix for 'a' is also addressed by this because the file will
     exist on disk with proper permissions before cloud-init writes it, and
     will thus keep the same ownership.

  [Test Case]
   * launch instance with landscape config in user-data like the following:
     #cloud-config
     apt_upgrade: True
     apt_sources:
      - source: deb $MIRROR $RELEASE-proposed main
     landscape:
       client:
         url: "https://landscape.canonical.com/message-system";
         ping_url: "http://landscape.canonical.com/ping";
         data_path: "/var/lib/landscape/client"
         http_proxy: "http://my.proxy.com/foobar";
         tags: "server,cloud"
   * upon investigation, /etc/landscape/client.conf should be owned
     by 'landscape' user rather than root.

  [Regression Potential]
   * If a user with a generic user_data setup is assuming that the 'landscape' config will be applied only on those images which already have landscape-client installed, automatically installing landscape-client will be an unexpected a behavior change.

  === End SRU Information ===

  When cloud-init runs and landscape-client is not installed, it creates
  /etc/landscape/client.conf owned as root:root, whereas landscape-
  client expects it to be landscape:root. The proper fix is although
  probably to require installation of landscape-client first, as it will
  create the file properly, and then landscape-client can update it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1066115/+subscriptions