'maas-run-scripts report-results' uses Debian tooling and is not distro-agnostic

[Chuan Li]

How to reproduce:

0) install 3 VMs. All 3 VMs are connected to the same virt bridge. I disable the virt dhcp and assign 3 static IPs to 3 VMs(same subnet)

A: CentOS7
B: Ubuntu 20.04
C: Ubuntu 20.04 (install the latest MAAS 3.1.0-10901-g.f1f8f1505-0ubuntu1~20.04.1 on it)

1) enlist CentOS7 following [1].
After running 'maas-run-scripts report-results', machines read show "status_message": "Script - 50-maas-01-commissioning failed" and CPU/ram/network/storage are all empty(NO-machine-information.png)
Detail steps are in enlist-centos-steps.txt

2) enlist Ubuntu 20.04 following same procedures. Results look good to me.
Detail steps are in enlist-ubuntu-steps.txt

maas logs are in maas-log.txt

[1] https://maas.io/docs/snap/3.1/ui/whats-new-in-maas#heading--enlist-deployed-machines

[Alberto Donato (ack)]

This seems to be the culprit:

2022-02-24 08:31:48 metadataserver.api: [critical] mymachine.maas(aka44t): commissioning script '50-maas-01-commissioning' failed during post-processing.
 Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/metadataserver/api.py", line 817, in signal
     target_status = process(node, request, status)
   File "/usr/lib/python3/dist-packages/metadataserver/api.py", line 641, in _process_commissioning
     self._store_results(
   File "/usr/lib/python3/dist-packages/metadataserver/api.py", line 529, in _store_results
     script_result.store_result(
   File "/usr/lib/python3/dist-packages/metadataserver/models/scriptresult.py", line 376, in store_result
     signal_status = try_or_log_event(
 --- <exception caught here> ---
   File "/usr/lib/python3/dist-packages/metadataserver/api.py", line 447, in try_or_log_event
     func(*args, **kwargs)
   File "/usr/lib/python3/dist-packages/metadataserver/builtin_scripts/hooks.py", line 932, in process_lxd_results
     raise ValueError(f"{e}: {output}")
 builtins.ValueError: Expecting value: line 1 column 1 (char 0): b''

[Alberto Donato (ack)]

Could you please also include the output of the 50-maas-10-commissioning script for the failing machine?

[Chuan Li (lccn)]

stdout and yaml are empty and stderr shows "Failed to parse /tmp/tmpvfa6obeu/resources.json: Expecting value: line 1 column 1 (char 0)"
You could check screenshot 50-maas-10-commissioning.png

[Alberto Donato (ack)]

What about 40-maas-01-machine-resources? Can you paste the output/error for it?

Also, do you have a custom script for storage configuration that runs between these two?

[Chuan Li (lccn)]

There is no custom script.

40-maas-01-machine-resources stderr:

/tmp/tmpvfa6obeu/scripts/commissioning/40-maas-01-machine-resources: line 29: dpkg: command not found

40-maas-01-machine-resources stdout: empty

[Alberto Donato (ack)]

Ah, there it is. The script is using dpkg, so it currently fails on distros that are not Debian-based

[Heather Lemon (hypothetical-lemon)]

Is there any known workarounds? other than not use Debain-based distro

[Thomas Lescot (tomm312)]

Same issue for me on an Ubuntu machine :

50-maas-01-commissioning

Failed to parse /tmp/tmpvc2uyq9x/resources.json: Expecting value: line 1 column 1 (char 0)
Thu, 20 Jan. 2022 13:55:38 Script result lookup or storage error - Failed processing commissioning data: invalid JSON data

Thu, 20 Jan. 2022 13:55:38 Script result lookup or storage error - ogdcjct-s01.gdc.local(m4bnrg): commissioning script '50-maas-01-commissioning' failed during post-processing.

In fact, the file "resources.json" is empty because the script 40 (local inventory) is not executed.

Workaround (manual scripts download and execution):
wget "http://<MAASIP>:5240/MAAS/machine-resources/amd64" -O "resources_bin" >&2
chmod +x resources_bin

wget http://<MAASIP>:5240/MAAS/maas-run-scripts
chmod 755 maas-run-scripts

Add the line "os.system('sudo /home/username/resources_bin > ' + str(paths.resources_file))"
to maas-run-scripts like this :

 result = script.run(console_output=ns.debug)
os.system('sudo /home/adm_gdc/resources_bin > ' + str(paths.resources_file))
 if ns.debug:

Run the script in sudo :

sudo ./maas-run-scripts report-results --config u1-creds.yaml

If that could help

[Thomas Lescot (tomm312)]

Despite this workaround, all informations are not reported to maas for network and storage

[Chuan Li (lccn)]

Try the w/a on centos7.