Neil,
I'm curious as to what you tihnk the right behavior would be here.
a.) add the netdev user
b.) fail as it does now.
** Changed in: cloud-init (Ubuntu)
Status: New = Triaged
** Changed in: cloud-init (Ubuntu)
Importance: Undecided = Medium
--
You received this bug
Is the netdev *group* used by Ubuntu server?
The way I've done it myself prior to Quantal is to delegate the problem
to the user-setup package.
add_default_user() {
echo Setting up '${CLOUD_DEFAULT_USERNAME}' default user
debconf-set-selections EOF
user-setup
I'm not sure I understand.
The way to handle this in cloud-init now is just to be more explicit with your
user-data or config (/etc/cloud/cloud.cfg.d).
#cloud-config
groups:
- foogroup
users:
- name: ubuntu
primary-group: foogroup
Then you'll get what you asked for.
In the past if the user
Why are you creating a default user in the 'netdev' group by default
when the standard Ubuntu server installation doesn't appear to create
that group?
That doesn't make any sense. It's always going to fail.
On 24 September 2012 16:24, Scott Moser smo...@ubuntu.com wrote:
I'm not sure I
On Mon, 24 Sep 2012, Neil Wilson wrote:
Why are you creating a default user in the 'netdev' group by default
when the standard Ubuntu server installation doesn't appear to create
that group?
I suppose this is probably for historical reasons. For all versions of
our cloud images (hardy+),
On 24 September 2012 18:10, Scott Moser smo...@ubuntu.com wrote:
I suppose this is probably for historical reasons. For all versions of
our cloud images (hardy+), there was a 'netdev' user in which the 'ubuntu'
was present (it is added by 'vmbuilder').
But the current stuff uses live-build -
--
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/1054035
Title:
Adding default user fails due to lack of 'netdev' group
To manage notifications about this bug go to:
