Node fails to commission with error in region controller re: '50-maas-01-commissioning' failed during post-processing

Bug #1939340 reported by Patrick McClory
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
High
Alberto Donato
3.0
Fix Released
High
Alberto Donato

Bug Description

When Commissioning a new node (dell r620) it fails without noting an error in the MaaS UI on the `50-maas-01-commissioning` stage. An exception is identified in the region controller's regiond.log:

```
2021-08-09 15:39:11 metadataserver.api: [critical] close-fly.fdcservers.maas(68fepw): 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 820, 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 384, 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 919, in process_lxd_results
     _process_lxd_resources(node, data)
   File "/usr/lib/python3/dist-packages/metadataserver/builtin_scripts/hooks.py", line 591, in _process_lxd_resources
     update_node_devices(
   File "/usr/lib/python3/dist-packages/metadataserver/builtin_scripts/hooks.py", line 549, in update_node_devices
     _process_usb_devices(add_func, data)
   File "/usr/lib/python3/dist-packages/metadataserver/builtin_scripts/hooks.py", line 472, in _process_usb_devices
     [
 builtins.TypeError: 'NoneType' object is not iterable
```

Combined log output is attached.

Tags: trivial

Related branches

Revision history for this message
Patrick McClory (pmd3v) wrote :
Revision history for this message
Bill Wear (billwear) wrote :

it may be in your log output somewhere, but which version of MAAS are you using?

Changed in maas:
status: New → Incomplete
Revision history for this message
Patrick McClory (pmd3v) wrote :

v3.0.0-10029-g.986ea3e45

Revision history for this message
Björn Tillenius (bjornt) wrote :

Ok, so the devices has "null" as value, where MAAS expects it to not be there at all.

Changed in maas:
status: Incomplete → Triaged
importance: Undecided → High
tags: added: trivial
Revision history for this message
Daniel Coultas (dcoultas) wrote :

running into this same issue.
Is there a work around currently for this issue?

Alberto Donato (ack)
Changed in maas:
milestone: none → 3.1.0
Alberto Donato (ack)
Changed in maas:
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Alberto Donato (ack)
Changed in maas:
assignee: nobody → Alberto Donato (ack)
Bill Wear (billwear)
Changed in maas:
milestone: 3.1.0 → 3.1.0-beta5
Changed in maas:
status: Fix Committed → Fix Released
Revision history for this message
Heitor Alves de Siqueira (halves) wrote :

MAAS 3.0.1 has now been released, and is available as below:
- deb: ppa:maas/3.0 (3.0.1-10052-g.82c730c57-0ubuntu1~20.04.1)
- snap: 3.0/stable (3.0.1-10052-g.82c730c57)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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