yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1070345@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/1070345

Title:
  need to restart landscape after updating config

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
Status in “cloud-init” source package in Raring:
  Fix Released

Bug description:
  === Begin SRU Information ===
  [Impact]
   * When landscape-client is installed in an image (default for ubuntu cloud
     images) there is a potential race where cloud-init will update the
     /etc/landscape/client.conf after landscape-client has started.  If it
     does so, then landscape-client will not register until the next reboot.
   * The fix here is simply to restart lanscape-client after writing config

  [Test Case]
   * This is a race condition, so it will not always occur, but generally you
     can see it by launching an Ubuntu cloud image, and providing it with
     lanscape-client configuration like the user-data below, and then expecting
     that system to correctly register itself.
     #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"

  [Regression Potential]
   * landscape-client could not behave well when 'restart' is requested
     right after it had started.   If that was the case, this could result
     in a race where the fix didn't actually accomplish what we wanted.
   * There is very little potential for regression other than in the
     case where the user was trying to register instance with landscape.

  === End SRU Information ===

  
  After installing landscape, or otherwise configuring it, cloud-init needs to restart the service.

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