[Bug 1042758] Re: landscape handler needs to set RUN=1 in /etc/default/landscape-client

[Scott Moser]

The fix to 12.04 was uploaded on Wednesday in cloud-
init_0.6.3-0ubuntu1.1.


** Description changed:

+ ==== Begin SRU Information ===
+ [IMPACT]
+  * explanation: The prevents people using cloud-init and Landscape to automatically register instances.  The configuration will be updated, but Landscape won't start, thus forcing people to either write additional code or manually go the instances.
+  * justification: without this landscape integration of cloud instances requires further effort by the user
+  * Fix: the fix is simple, it writes 'RUN=1' to /etc/default/landscape-client if and only if landscape configuration is given.
+ 
+ [TESTCASE]
+ To reproduce the problem, create a cloud-init configuration with Landscape credentials:
+ #cloud-config
+ landscape:
+  - account_name: "$host_account"
+  - computer_title: "Test instance"
+  - cloud: true
+ 
+ Using the released version, the configuration will be written, but the
+ client won't start and the instance won't register. With the fixed
+ version, the client will start and register to Landscape hosted.
+ 
+ The change is minimal and only impact the Landscape portion of the code.
+ https://code.launchpad.net/~therve/cloud-init/fix-landscape-
+ config/+merge/122870 contains the relevant changeset.
+ 
+ [Regression Potential]
+  * There is very little potential for regression here.  The changes modified path is only taken if there is landscape configuration given to cloud-init.
+ 
+ ==== End SRU Information ===
+ 
  The landscape handler needs to also set RUN=1 in /etc/default/landscape-
  client. Without it, the initscript /etc/init.d/landscape-client won't
  start the service.

** Changed in: cloud-init (Ubuntu Precise)
       Status: Confirmed => In Progress

** Description changed:

  ==== Begin SRU Information ===
  [IMPACT]
-  * explanation: The prevents people using cloud-init and Landscape to automatically register instances.  The configuration will be updated, but Landscape won't start, thus forcing people to either write additional code or manually go the instances.
-  * justification: without this landscape integration of cloud instances requires further effort by the user
-  * Fix: the fix is simple, it writes 'RUN=1' to /etc/default/landscape-client if and only if landscape configuration is given.
+  * explanation: The prevents people using cloud-init and Landscape to automatically register instances.  The configuration will be updated, but Landscape won't start, thus forcing people to either write additional code or manually go the instances.
+  * justification: without this landscape integration of cloud instances requires further effort by the user
+  * Fix: the fix is simple, it writes 'RUN=1' to /etc/default/landscape-client if and only if landscape configuration is given.
  
  [TESTCASE]
  To reproduce the problem, create a cloud-init configuration with Landscape credentials:
  #cloud-config
  landscape:
-  - account_name: "$host_account"
-  - computer_title: "Test instance"
-  - cloud: true
+  - account_name: "$host_account"
+  - computer_title: "Test instance"
+  - cloud: true
  
  Using the released version, the configuration will be written, but the
  client won't start and the instance won't register. With the fixed
  version, the client will start and register to Landscape hosted.
  
  The change is minimal and only impact the Landscape portion of the code.
  https://code.launchpad.net/~therve/cloud-init/fix-landscape-
  config/+merge/122870 contains the relevant changeset.
  
+ The user-data at http://paste.ubuntu.com/1256164/ should result in the
+ ppa being added, cloud-init being upgraded, and the new code correctly
+ being used.
+ 
  [Regression Potential]
-  * There is very little potential for regression here.  The changes modified path is only taken if there is landscape configuration given to cloud-init.
+  * There is very little potential for regression here.  The changes modified path is only taken if there is landscape configuration given to cloud-init.
  
  ==== End SRU Information ===
  
  The landscape handler needs to also set RUN=1 in /etc/default/landscape-
  client. Without it, the initscript /etc/init.d/landscape-client won't
  start 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/1042758

Title:
  landscape handler needs to set RUN=1 in /etc/default/landscape-client

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