Comment 0 for bug 1903544
Revision history for this message
| Bart Vrancken (bartvrancken) wrote Commissioning failed without error | #0 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
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.
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.