MAAS nodes that fail commissioning continue to use stale commissioning scripts

Bug #2083076 reported by slines
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Triaged
High
Unassigned
3.5
Triaged
High
Unassigned

Bug Description

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.

Revision history for this message
slines (slines) wrote :
Revision history for this message
Nick De Villiers (nickdv99) wrote :

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?

Changed in maas:
status: New → Incomplete
Revision history for this message
Andrew Lamzed-Short (andyls) wrote :

slines, does this bug still occur for you? If so, please provide us with the build steps you used to setup and configure your MAAS environment so that we may reproduce the issue and help get it resolved for you.

Changed in maas:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Jacopo Rota (r00ta) wrote :

Multiple people are facing this https://bugs.launchpad.net/maas/+bug/2091554 but we still need a reproducer

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → High
milestone: none → 3.6.x
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.