Activity log for bug #1788430
| Date | Who | What changed | Old value | New value | Message |
|---|---|---|---|---|---|
| 2018-08-22 15:49:38 | Andres Rodriguez | bug | added bug | ||
| 2018-08-22 15:49:42 | Andres Rodriguez | maas: importance | Undecided | High | |
| 2018-08-22 15:49:44 | Andres Rodriguez | maas: status | New | Triaged | |
| 2018-08-22 15:49:48 | Andres Rodriguez | maas: importance | High | Critical | |
| 2018-08-22 15:49:50 | Andres Rodriguez | maas: milestone | 2.5.0alpha2 | ||
| 2018-08-22 15:50:00 | Andres Rodriguez | summary | [2.5] Newly created VM's | [2.5] Newly created VM's end up with "Error: Node must be connected to a network." | |
| 2018-08-22 15:52:21 | Andres Rodriguez | description | I added a pod and composed machines. Those machines commissioned but the network information was not updated. The UI showed: Error: Node must be connected to a network. After I manually commissioned the machine, the network was correctly attached. I believe this is because on new compose it may be telling MAAS to retain network configuration? | I added a pod and composed machines. Those machines commissioned but the network information was not updated. The UI showed: Error: Node must be connected to a network. After I manually commissioned the machine, the network was correctly attached. I believe this is because on new compose it may be telling MAAS to retain network configuration? The machine was composed with: maas <user> pod compose <pod-id> hostname=foo cores=X memory=2048 | |
| 2018-08-22 17:06:14 | Launchpad Janitor | merge proposal linked | https://code.launchpad.net/~mpontillo/maas/+git/maas/+merge/353587 | ||
| 2018-08-22 22:51:31 | Mike Pontillo | maas: assignee | Mike Pontillo (mpontillo) | ||
| 2018-08-23 02:03:03 | MAAS Lander | maas: status | Triaged | Fix Committed | |
| 2018-08-23 13:45:25 | Andres Rodriguez | maas: status | Fix Committed | Fix Released |
