Proxmox Vm and MaaS power management type - proxmox

[mrk131211]

Hi,
I am trying to provision and deploy a Proxmox vm by MaaS. VM was able to PXE boot by MaaS and able to deploy Ubuntu 20.04 LTS image- with power management type as manual. My Mass Vm is in proxmox itself.

I heard that Maas supports power management type as proxmox and i tried that and it was not working for me. All the permissions are added correctly along with proxmox api key. Is this a limitation of the Proxmox power driver in Maas or do i have to install any proxmox driver that allows maas. - https://coldnorthadmin.com/posts/maas_proxmox_power/

I am attaching the event log.

[troyanov]

Hi @mrk131211

I think the easiest way to troubleshoot this issue would be adding a print statement, and examine what was returned in the response_data

https://github.com/maas/maas/blob/afb74686288cae0d767d6a338e66c1c06893986d/src/provisioningserver/drivers/power/proxmox.py#L277C24-L277C48

Du you have MAAS installed via snap or deb package?

If it is a deb, simply modify this file:
.../provisioningserver/drivers/power/proxmox.py

If it is a snap, then you can check this post:

Rebuilding MaaS snap : [Errno 111] Connection refused

Hello Everyone, We may have to do light modifications about MaaS curtin generation. For this purpose we may have to rebuild the snap. So we have done this trial, for sure, modifying nothing at first, to see if it is doable: On a fresh machine we do : sudo unsquashfs maas_23947.snap sudo snap pack ./squashfs-root Then in place of doing: sudo snap ack maas_23947.snap sudo snap install maas_23947.snap We do: sudo snap install --dangerous maas_3.2.6-12016-g.19812b4da_amd64.snap Then we fol…

[rodger-duffett]

Check that the token name contains the login realm. I could not get it to work without this despite the documentation saying that it should not be included. I did put in a pull request for this to be amended.
For me it looks like this:

[mrk131211]

Hii Troyanov,

Thanks for your reply.
The MAAS is installed via snap. I will go through the post you shared.

Thank you.

[mrk131211]

Hii rodger-duffett,

Thanks for your reply.
I added Just like in the screenshot the you have shared. Still not working! Have you done any configuration changes in MAAS. ?

Thankyou

[rodger-duffett]

Hi,
No configuration changes in MAAS. I am using version 3.4.0~rc1.
The other thing to check is that your API token has the right permissions to your VM tree. It should look something like this:

Also make sure that you have set the right VM Node ID number in the MAAS machine power type config. In my screenshot it is 105 but this must match the VM that you are working with.