The content event log shows the node transitioned from 'Allocated' to 'Deploying'; but when the node PXE booted, it seems the node was 'Allocated'. The weird part is that the node event log doesn't show the transition from 'Deploying' back to 'Allocated'; these node transition events are tied to Django's internals and thus I see two possible causes for this:
- something outside Django (i.e. outside MAAS) changed the node's status (very unlikely)
- the transaction 'Allocated' → 'Deploying' got rolled back. This is strange because this is part of the "start node" request and we see it succeeded (return code 200 in apache's log). It's worth investigating how the recent work that introduced maybe_change_power_state can roll the DB transaction back and still power up the node.
The content event log shows the node transitioned from 'Allocated' to 'Deploying'; but when the node PXE booted, it seems the node was 'Allocated'. The weird part is that the node event log doesn't show the transition from 'Deploying' back to 'Allocated'; these node transition events are tied to Django's internals and thus I see two possible causes for this: power_state can roll the DB transaction back and still power up the node.
- something outside Django (i.e. outside MAAS) changed the node's status (very unlikely)
- the transaction 'Allocated' → 'Deploying' got rolled back. This is strange because this is part of the "start node" request and we see it succeeded (return code 200 in apache's log). It's worth investigating how the recent work that introduced maybe_change_