Activity log for bug #1811836
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2019-01-15 14:17:12 | Björn Tillenius | bug | added bug | ||
| 2019-01-15 14:17:22 | Björn Tillenius | maas: status | New | Triaged | |
| 2019-01-15 14:17:26 | Björn Tillenius | maas: importance | Undecided | Medium | |
| 2019-01-15 14:17:28 | Björn Tillenius | maas: milestone | 2.5.1 | ||
| 2019-01-15 14:17:35 | Björn Tillenius | tags | api | ||
| 2019-01-16 07:31:18 | Andres Rodriguez | maas: milestone | 2.5.1 | 2.5.2 | |
| 2019-02-21 16:20:13 | Andres Rodriguez | maas: milestone | 2.5.2 | 2.5.3 | |
| 2019-02-21 16:20:19 | Andres Rodriguez | maas: milestone | 2.5.3 | 2.5.2 | |
| 2019-03-05 23:09:19 | Andres Rodriguez | maas: milestone | 2.5.2 | 2.5.3 | |
| 2019-05-03 16:10:13 | Andres Rodriguez | maas: milestone | 2.5.3 | 2.5.4 | |
| 2019-05-31 14:26:50 | Andres Rodriguez | maas: milestone | 2.5.4 | ||
| 2023-04-06 09:01:13 | Jerzy Husakowski | maas: milestone | 3.4.0 | ||
| 2023-04-06 09:01:22 | Jerzy Husakowski | summary | [2.5, API] allocate command doesn't respect system_id and name when a pod is registered | allocate command doesn't respect system_id and name when a pod is registered | |
| 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. | |
| 2023-06-29 08:33:27 | Alberto Donato | maas: milestone | 3.4.0 | 3.4.x | |
| 2024-03-05 14:51:03 | Anton Troyanov | maas: milestone | 3.4.x | 3.5.x | |
| 2024-03-14 08:01:53 | Anton Troyanov | nominated for series | maas/3.4 | ||
| 2024-03-14 08:01:53 | Anton Troyanov | bug task added | maas/3.4 | ||
| 2024-03-14 08:01:58 | Anton Troyanov | maas/3.4: status | New | Won't Fix | |
| 2024-03-14 08:01:59 | Anton Troyanov | maas/3.4: importance | Undecided | Medium | |
| 2024-07-12 09:56:31 | Anton Troyanov | nominated for series | maas/3.6 | ||
| 2024-07-12 09:56:31 | Anton Troyanov | bug task added | maas/3.6 | ||
| 2024-07-12 09:56:31 | Anton Troyanov | nominated for series | maas/3.5 | ||
| 2024-07-12 09:56:31 | Anton Troyanov | bug task added | maas/3.5 | ||
| 2024-07-12 09:58:13 | Anton Troyanov | maas/3.5: status | New | Won't Fix | |
| 2024-07-12 09:58:15 | Anton Troyanov | maas/3.5: importance | Undecided | Medium | |
| 2024-07-12 09:58:17 | Anton Troyanov | maas/3.6: milestone | 3.5.x | 3.6.x |
