[Bug 1070345] Re: need to restart landscape after updating config

[Scott Moser]

** Description changed:

- After installing landscape, or otherwise configuring it, cloud-init
- needs to restart the service.
+ === 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.

-- 
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/1070345

Title:
  need to restart landscape after updating config

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