Activity log for bug #1590991
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2016-06-09 23:33:12 | Mike Pontillo | bug | added bug | ||
| 2016-06-09 23:33:16 | Mike Pontillo | maas: milestone | 2.0.0 | ||
| 2016-06-09 23:36:16 | Launchpad Janitor | branch linked | lp:~mpontillo/maas/node-allocate-by-system-id-plus-doc-fixes-1590991 | ||
| 2016-06-10 13:43:03 | Scott Moser | description | When using the "machines allocate" API, there was no way to allocate a node based on its system_id. I first had to look up the hostname. (which could change between API calls, so isn't reliable.) | When using the "machines allocate" API, there was no way to allocate a node based on its system_id. I first had to look up the hostname. (which could change between API calls, so isn't reliable.) Related bugs: * bug 1074317: cmdline acquire and start is difficult | |
| 2016-06-10 15:58:59 | Andres Rodriguez | summary | Cannot allocate a node based on its system_id | [2.0b6] Cannot allocate a node based on its system_id | |
| 2016-06-11 00:04:47 | MAAS Lander | maas: status | Triaged | Fix Committed | |
| 2016-08-18 11:26:01 | Andres Rodriguez | maas: status | Fix Committed | Fix Released |
