| 2023-04-06 12:42:43 |
Björn Tillenius |
description |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1.
I have a normal user and a machine A that is allocated to another user.
There's also a pod registered that has capacity to create new VMs.
If I use the allocate API like this:
maas non-admin machines allocate name=A
I get a machine from the pod. The same happens if I specify the system_id instead.
This is wrong, since the resulting machine doesn't match the constraint I specified. |
This is with MAAS 2.5.1-7489-g2f25a2cc0-0ubuntu1~18.04.1.
I have a normal user and a machine A that is allocated to another user.
There's also a pod registered that has capacity to create new VMs.
If I use the allocate API like this:
maas non-admin machines allocate name=A
I get a machine from the pod. The same happens if I specify the system_id instead.
This is wrong, since the resulting machine doesn't match the constraint I specified.
The machine that you get back has an automatically generated name.
With MAAS 3.3, it seems that passing a non-existing system_id does indeed fail as expected, but passing in a non-existing name still gives you a (virtual) machine. |
|
