MAAS cluster controller runs as wrong groups
Bug #1319609 reported by
Jeroen T. Vermeulen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Low
|
Unassigned | ||
| maas (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
On IRC, jefferai notes that it's hard to get the virsh power method working, even when the maas user is a member of libvirtd and the system has rebooted to make the changes take effect.
Turns out that the cluster controller runs as maas, but not with the right set of groups. It gets started as root, then drops privileges but doesn't assume the full "maas" user identity.
A surprising workaround is to add "root" to the libvirtd group.
Revision history for this message
| Julian Edwards (julian-edwards) wrote | #1 |
| Changed in maas: | |
| status: | Triaged → Invalid |
| summary: |
- Document: to use MAAS with virsh, add root to libvirtd group + MAAS cluster controller runs as wrong groups |
To post a comment you must log in.
That, therefore, makes this a packaging bug.