MAAS fails to use virsh when managing virtual nodes
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
maas (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Raring |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
MAAS fails to start/stop virtual nodes when using virsh. This is because MAAS lacks permissions to run virsh.
[Solution]
The solution is to run virsh with sudo, as well as allowing the 'maas' user to run 'virsh' in the sudoers file.
[Test Case]
To reproduce do the following:
1. install MAAS and configure local KVM nodes with it.
2. Confiugure the power pameters in MAAS.
3. Deploy a node.
Without the fix the node will be never turned on/off and /var/log/
[Regression Potential]
Minimal. This has been tested in our labs. And this actually fixes something that is currently broken and won't work out of the box. The MAAS team and Server team are dedicated to perform any corrective actions in the events of a regression.
[2013-04-23 11:20:21,482: ERROR/MainProcess] Task provisioningser
Traceback (most recent call last):
File "/usr/lib/
R = retval = fun(*args, **kwargs)
File "/usr/lib/
issue_
File "/usr/lib/
pa.
File "/usr/lib/
self.
File "/usr/lib/
raise PowerActionFail
PowerActionFail: PowerActionFail()
With the fix, nodes will be turned on/off successfully.
description: | updated |
Hi, this is missing Regression Potential. Please see https:/ /wiki.ubuntu. com/StableRelea seUpdates# Procedure for more information.