ubuntu user not in 'lxd' group on xenial instances

Bug #1580714 reported by Cheryl Jennings
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Canonical Juju
Expired
Medium
Unassigned

Bug Description

When Juju provisions a machine, it writes out the groups for the ubuntu user, which overwrites any groups the ubuntu user had previously. For the case of xenial, this includes the lxd group.

Users entry in cloud config:
users:
- groups:
    - adm
    - audio
    - cdrom
    - dialout
    - dip
    - floppy
    - netdev
    - plugdev
    - sudo
    - video
    lock_passwd: true
    name: ubuntu

The groups are defined in cloudconfig/userdatacfg_unix.go:
        // UbuntuGroups is the set of unix groups to add the "ubuntu" user to
        // when initializing an Ubuntu system.
        UbuntuGroups = []string{"adm", "audio", "cdrom", "dialout", "dip",
                "floppy", "netdev", "plugdev", "sudo", "video"}

tags: added: juju-release-support lxd
Revision history for this message
John A Meinel (jameinel) wrote :

Do we need ro specialize this per OS since on Trusty the lxd group won't exist before LXD is installed (while on Xenial it is there by default). Is it possible to just not pass anything here and use the defaults?

Revision history for this message
Cheryl Jennings (cherylj) wrote :

I would say just use the defaults, but I haven't done testing to verify that it works properly if we do that. I don't know the history of why we specify the groups.

Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta7 → 2.0-beta8
Changed in juju-core:
milestone: 2.0-beta8 → 2.0-beta9
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta9 → 2.0-beta10
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 2.0-beta10 → 2.0-beta11
Changed in juju-core:
importance: High → Medium
milestone: 2.0-beta11 → none
affects: juju-core → juju
Revision history for this message
Canonical Juju QA Bot (juju-qa-bot) wrote :

This bug has not been updated in 5 years, so we're marking it Expired. If you believe this is incorrect, please update the status.

Changed in juju:
status: Triaged → Expired
tags: added: expirebugs-bot
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.