| 2012-08-28 14:04:54 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2012-09-05 13:17:59 |
Thomas Herve |
branch linked |
|
lp:~therve/cloud-init/fix-landscape-config |
|
| 2012-09-05 13:18:02 |
Thomas Herve |
cloud-init: assignee |
|
Thomas Herve (therve) |
|
| 2012-09-05 13:18:08 |
Thomas Herve |
cloud-init: status |
New |
In Progress |
|
| 2012-09-05 20:41:02 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2012-09-05 20:59:03 |
Scott Moser |
cloud-init: status |
In Progress |
Fix Committed |
|
| 2012-09-19 17:39:55 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2012-09-19 17:40:19 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
In Progress |
|
| 2012-09-19 17:40:26 |
Scott Moser |
nominated for series |
|
Ubuntu Precise |
|
| 2012-09-19 17:40:26 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Precise) |
|
| 2012-09-19 17:41:09 |
Launchpad Janitor |
cloud-init (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-09-20 02:10:10 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
In Progress |
Fix Released |
|
| 2012-09-24 17:28:36 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2012-09-24 17:28:39 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
High |
|
| 2012-09-24 17:28:41 |
Scott Moser |
cloud-init (Ubuntu Precise): importance |
Undecided |
High |
|
| 2012-09-24 17:30:02 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-init |
|
| 2012-10-01 18:25:33 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2012-10-02 13:59:25 |
Thomas Herve |
branch linked |
|
lp:~therve/cloud-init/fix-landscape-config-precise |
|
| 2012-10-05 15:24:01 |
Scott Moser |
description |
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. |
==== 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. |
|
| 2012-10-05 15:28:19 |
Scott Moser |
cloud-init (Ubuntu Precise): status |
Confirmed |
In Progress |
|
| 2012-10-05 15:29:21 |
Scott Moser |
description |
==== 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. |
==== 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.
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.
==== 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. |
|
| 2012-10-12 18:41:52 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/precise/cloud-init/sru |
|
| 2012-10-17 20:49:33 |
Clint Byrum |
cloud-init (Ubuntu Precise): status |
In Progress |
Fix Committed |
|
| 2012-10-17 20:49:36 |
Clint Byrum |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-10-17 20:49:38 |
Clint Byrum |
bug |
|
|
added subscriber SRU Verification |
| 2012-10-17 20:49:41 |
Clint Byrum |
tags |
|
verification-needed |
|
| 2012-11-06 20:41:00 |
Scott Moser |
tags |
verification-needed |
verification-done |
|
| 2012-11-07 22:02:56 |
Clint Byrum |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2012-11-07 22:03:26 |
Launchpad Janitor |
cloud-init (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2013-08-28 11:32:39 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-proposed |
|
| 2023-05-09 21:32:20 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2289 |
|
