Activity log for bug #1903544

Date Who What changed Old value New value Message
2020-11-09 15:09:26 Bart Vrancken bug added bug
2020-11-09 15:24:18 Bart Vrancken description We have special purpose PCB's with Intel J4105 CPU and storage, etc. Running the Commisisioning it fails at the step: Script result lookup or storage error - fresh-collie.nl.pha.farm(w7bb3y): commissioning script '50-maas-01-commissioning' failed during post-processing The problem here is that it does not log why. There are no errors in the log on the controller ... only the returned YML data from the tool collecting the hardware info and in stderror it logs the download itself. I have compared this with other systems and the format looks identical. when i boot the unit into rescue mode it works fine, and running the script manually did not provide any errors and outputted the same YAML data. The YAML data both in controller as locally outputted was verified to be valid YAML format. Looking at the region controller dashboard for the node's inventory i do notice the amount of cores + speed are listed as 'unknown' while on the next line it does report the exact CPU type. For Memory it also says 'unknown'. The YAML data does contain this information though. Since the error says post-processing i would think this is something at the region controller, however i would suspect such logs are included ... exspecially if there are errors. We have special purpose PCB's with Intel J4105 CPU and storage, etc. Running the Commisisioning it fails at the step: Script result lookup or storage error - fresh-collie.nl.pha.farm(w7bb3y): commissioning script '50-maas-01-commissioning' failed during post-processing The problem here is that it does not log why. There are no errors in the log on the controller ... only the returned YML data from the tool collecting the hardware info and in stderror it logs the download itself. I have compared this with other systems and the format looks identical. when i boot the unit into rescue mode it works fine, and running the script manually did not provide any errors and outputted the same YAML data. The YAML data both in controller as locally outputted was verified to be valid YAML format. Looking at the region controller dashboard for the node's inventory i do notice the amount of cores + speed are listed as 'unknown' while on the next line it does report the exact CPU type. For Memory it also says 'unknown'. The YAML data does contain this information though. Since the error says post-processing i would think this is something at the region controller, however i would suspect such logs are included ... exspecially if there are errors. The commissioning YAML output can be found at https://8n1.org/18077/43f3
2020-11-09 19:44:41 Lee Trager maas: status New Incomplete
2020-11-18 15:19:59 Nobuto Murata bug added subscriber Nobuto Murata
2020-11-18 15:32:30 Nobuto Murata summary Commissioning failed without error 50-maas-01-commissioning failed with "Node with this Hardware uuid already exists"
2020-11-18 15:32:50 Nobuto Murata maas: status Incomplete New
2020-11-18 15:59:37 Nobuto Murata marked as duplicate 1893690