| 2012-10-12 20:26:51 |
Thomas Herve |
bug |
|
|
added bug |
| 2012-10-12 21:07:10 |
Scott Moser |
cloud-init: importance |
Undecided |
Medium |
|
| 2012-10-12 21:07:10 |
Scott Moser |
cloud-init: status |
New |
Triaged |
|
| 2012-10-15 08:22:38 |
Thomas Herve |
description |
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 updated it. |
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. |
|
| 2012-10-15 08:26:15 |
Thomas Herve |
branch linked |
|
lp:~therve/cloud-init/landscape-conf-permissions |
|
| 2012-10-15 17:43:27 |
Launchpad Janitor |
branch linked |
|
lp:cloud-init |
|
| 2012-11-06 19:03:48 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu) |
|
| 2012-11-06 19:04:06 |
Scott Moser |
nominated for series |
|
Ubuntu Precise |
|
| 2012-11-06 19:04:06 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Precise) |
|
| 2012-11-06 19:04:06 |
Scott Moser |
nominated for series |
|
Ubuntu Quantal |
|
| 2012-11-06 19:04:06 |
Scott Moser |
bug task added |
|
cloud-init (Ubuntu Quantal) |
|
| 2012-11-06 19:17:19 |
Scott Moser |
cloud-init (Ubuntu Precise): status |
New |
Triaged |
|
| 2012-11-06 19:17:22 |
Scott Moser |
cloud-init (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2012-11-06 19:17:25 |
Scott Moser |
cloud-init (Ubuntu Quantal): status |
New |
Triaged |
|
| 2012-11-06 19:17:28 |
Scott Moser |
cloud-init (Ubuntu Quantal): importance |
Undecided |
Medium |
|
| 2012-11-06 19:17:32 |
Scott Moser |
cloud-init (Ubuntu): status |
New |
Triaged |
|
| 2012-11-06 19:17:34 |
Scott Moser |
cloud-init (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-11-06 20:08:11 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/precise/cloud-init/sru |
|
| 2012-11-07 15:47:49 |
Scott Moser |
cloud-init: status |
Triaged |
Fix Committed |
|
| 2012-11-08 19:08:40 |
Scott Moser |
description |
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. |
=== 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]
* This was broken before, so it is not likely to be broken worse now.
=== 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. |
|
| 2012-11-14 20:20:12 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/cloud-init |
|
| 2012-11-14 20:31:04 |
Scott Moser |
cloud-init: status |
Fix Committed |
Fix Released |
|
| 2012-11-14 21:11:11 |
Launchpad Janitor |
cloud-init (Ubuntu): status |
Triaged |
Fix Released |
|
| 2012-11-30 06:11:02 |
Launchpad Janitor |
branch linked |
|
lp:~smoser/ubuntu/quantal/cloud-init/sru |
|
| 2012-12-02 03:41:18 |
Scott Moser |
cloud-init (Ubuntu Quantal): status |
Triaged |
In Progress |
|
| 2012-12-02 03:41:23 |
Scott Moser |
cloud-init (Ubuntu Quantal): assignee |
|
Scott Moser (smoser) |
|
| 2012-12-10 21:32:55 |
Steve Langasek |
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]
* This was broken before, so it is not likely to be broken worse now.
=== 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. |
=== 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. |
|
| 2012-12-10 23:04:50 |
Steve Langasek |
cloud-init (Ubuntu Precise): status |
Triaged |
Fix Committed |
|
| 2012-12-10 23:04:52 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2012-12-10 23:04:54 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2012-12-10 23:04:57 |
Steve Langasek |
tags |
|
verification-needed |
|
| 2012-12-13 20:29:20 |
Clint Byrum |
cloud-init (Ubuntu Quantal): status |
In Progress |
Fix Committed |
|
| 2013-01-09 11:23:06 |
Thomas Herve |
tags |
verification-needed |
verification-done |
|
| 2013-01-16 14:20:17 |
Launchpad Janitor |
cloud-init (Ubuntu Precise): status |
Fix Committed |
Fix Released |
|
| 2013-01-16 14:20:38 |
Colin Watson |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2013-01-16 14:21:09 |
Launchpad Janitor |
cloud-init (Ubuntu Quantal): status |
Fix Committed |
Fix Released |
|
| 2013-08-28 11:32:39 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-proposed |
|
| 2013-08-28 11:32:56 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/precise/cloud-init/precise-updates |
|
| 2013-08-28 11:33:11 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/quantal/cloud-init/quantal-proposed |
|
| 2023-05-09 21:36:16 |
James Falcon |
bug watch added |
|
https://github.com/canonical/cloud-init/issues/2307 |
|
