Version: maas/jammy,now 1:3.5.1-16317-g.409891638-0ubuntu1~22.04.1
Interface: UI
What happened: Nodes that are in the "Failed commissioning" state will continue to use old/cached commissioning scripts and ignore modifications to those scripts made through the UI. If you delete the failed node, re-enlist the node, and then commission the node, it will pick up the new version of the commissioning script.
Steps to reproduce: Upload a custom commissioning script like 42-my-custom-comissioning-script.py which contains a syntax error. Commission a new node and wait until it enters the failed to commission state when it executes the custom script. Deleted the 42-my-custom-comissioning-script.py from maas, correct the sytax error in 42-my-custom-comissioning-script.py, and re-uploaded it. Then do action->Commission on the node with failed commissioning, and it will re-execute the old script with the syntax error and not the new one that you uploaded. Delete the failed node, re-enlist the node, and then commission the node, and it will pick up the new version of the commissioning script.
Hey slines, thanks for the report!
I tried reproducing the issue with the steps you gave, but MAAS would always use the new copy of the script for me - could you provide me with the steps/commands you used to build and set up your MAAS environment?