Activity log for bug #1930002

Date Who What changed Old value New value Message
2021-05-28 13:51:43 Nathaniel W. Turner bug added bug
2021-05-28 13:53:12 Nathaniel W. Turner description MAAS 3.0-rc1. A newly-commissioned machine failed to deploy because the storage config was wrong. The only way to fix this was to first Release the machine back to the pool and then quickly Acquire it before anyone else tried to deploy it. Could perhaps "Abort..." be an available action for nodes in the "Failed to deploy" state, allowing them to transition directly to Allocated? MAAS 3.0-rc1. Personal severity level: "not a big deal" A newly-commissioned machine failed to deploy because the storage config was wrong. The only way to fix this was to first Release the machine back to the pool and then quickly Acquire it before anyone else tried to deploy it. Could perhaps "Abort..." be an available action for nodes in the "Failed to deploy" state, allowing them to transition directly to Allocated?
2021-05-28 14:43:56 Björn Tillenius maas: status New Triaged
2021-05-28 14:44:00 Björn Tillenius maas: importance Undecided Medium
2023-09-28 08:50:14 Jerzy Husakowski tags node-lifecycle
2023-09-28 08:51:35 Jerzy Husakowski maas: importance Medium Low
2023-09-28 08:51:35 Jerzy Husakowski maas: milestone 3.5.0
2024-03-05 15:32:43 Anton Troyanov maas: milestone 3.5.0 3.5.x
2024-07-12 09:16:06 Anton Troyanov nominated for series maas/3.6
2024-07-12 09:16:06 Anton Troyanov bug task added maas/3.6
2024-07-12 09:16:06 Anton Troyanov nominated for series maas/3.5
2024-07-12 09:16:06 Anton Troyanov bug task added maas/3.5
2024-07-12 09:17:34 Anton Troyanov maas/3.5: status New Won't Fix
2024-07-12 09:17:36 Anton Troyanov maas/3.5: importance Undecided Low
2024-07-12 09:17:37 Anton Troyanov maas/3.6: milestone 3.5.x 3.6.x