snap deployed maas is not able to use openstack nova power type due to missing python3-novaclient dependency
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Won't Fix
|
High
|
Unassigned | ||
3.3 |
Won't Fix
|
High
|
Unassigned |
Bug Description
This can be easily reproduced with a snap deployed maas environment (tested on versions 3.1 and 3.3). Attempt to add a machine with the `OpenStack Nova` power type, OpenStack instance UUID, tenant name, username, password, and Auth URL. After attaching the machine and clicking "Check Power", the status will change to "Power Error" and you will see the following in /var/snap/
maasserver.
Traceback (most recent call last):
File "/snap/
_inlineCallbacks(r, g, status)
File "/snap/
status.
File "/snap/
self._startRunC
File "/snap/
self._runCallba
--- <exception caught here> ---
File "/snap/
current.result = callback(
File "/snap/
failure.
File "/snap/
self.raiseExcep
File "/snap/
raise self.value.
File "/snap/
result = g.send(result)
File "/snap/
raise PowerActionFail(
provisioningser
Upon installing the python3-novaclient package on the rack controller (using apt), and rebooting the rack controller, the error persists.
Further, looking into the /snap/maas/
description: | updated |
Changed in maas: | |
status: | New → Confirmed |
status: | Confirmed → New |
Changed in maas: | |
status: | Triaged → Incomplete |
Changed in maas: | |
milestone: | 3.4.0 → 3.4.0-beta2 |
I was able to easily reproduce this. Since this is a snap installing the python3-novaclient package has no effect.