Comment 6 for bug 1751946

I am hitting this also, with MAAS 2.3.5.

Just one of the machines fails to deploy with this error:

Node failed to be deployed, because of the following error: {"current_testing_script_set": ["script set instance with id 2029 does not exist."]}
.

Also, commissioning yield similar error:

Node failed to be commissioned, because of the following error: {"current_testing_script_set": ["script set instance with id 2029 does not exist."]}

I was able to 'fix' this with suggestion from Andres - re-commissioning worked when I selected at least one test. After that deploying of that machine was fine.

I see that this particular machine was the only one that had 'offending' scriptset id of 2029.

I *think* this has to do with me testing commissioning scripts in the past, and removing them recently. However, I don't (yet) understand why just this particular machine was affected.

I'm running MAAS 2.3.5-6511-gf466fdb-0ubuntu1.