Rack controller fails to refresh due to 50-maas-01-commissioning post-processing failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
High
|
Newell Jensen |
Bug Description
I built master as a set of Debian packages and am running it in an LXD container. I noticed the following exception being raised in my MAAS logs.
There appears to be two bugs here
1. The LXD commissioning code always returns a blocksize of 0 when run in a container or not as root. This may be a permissions issue but could be something LXD could allow to be passed through.
2. Since all the other data is fine MAAS should be able to handle this case. One possible way would be to just default to 512 when 0 is returned.
machine-resources output in LXD container: http://
machine-resources output as a user on host: http://
machine-resource output as root on host: http://
2019-10-18 23:28:46 metadataserver.api: [critical] maas-bionic.
Traceback (most recent call last):
File "/usr/lib/
target_status = process(node, request, status)
File "/usr/lib/
node, node.current_
File "/usr/lib/
**args, timedout=(status == SIGNAL_
File "/usr/lib/
exit_
--- <exception caught here> ---
File "/usr/lib/
func(*args, **kwargs)
File "/usr/lib/
update_
File "/usr/lib/
firmware_
File "/usr/lib/
return getattr(
File "/usr/lib/
obj.
File "/usr/lib/
exclude=
File "/usr/lib/
raise ValidationError
django.
Related branches
- Lee Trager (community): Approve
- MAAS Lander: Pending (unittests) requested
-
Diff: 58 lines (+34/-2)2 files modifiedsrc/metadataserver/builtin_scripts/hooks.py (+5/-2)
src/metadataserver/builtin_scripts/tests/test_hooks.py (+29/-0)
description: | updated |
Changed in maas: | |
milestone: | none → 2.7.0alpha1 |
assignee: | nobody → Newell Jensen (newell-jensen) |
importance: | Undecided → High |
status: | New → Triaged |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |