[2.0a4] Disks less than 4MB in size cause a traceback on the MAAS server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Critical
|
Unassigned |
Bug Description
I came across the following traceback when running MAAS on my laptop using 'make run':
==> logs/regiond2/
2016-05-10 17:42:00 [maasserver] ERROR: #######
2016-05-10 17:42:00 [maasserver] ERROR: Traceback (most recent call last):
File "/usr/lib/
response = wrapped_
File "/home/
return view_atomic(*args, **kwargs)
File "/usr/lib/
return func(*args, **kwds)
File "/home/
response = upcall(request, *args, **kwargs)
File "/usr/lib/
response = func(*args, **kwargs)
File "/usr/lib/
result = self.error_
File "/usr/lib/
result = meth(request, *args, **kwargs)
File "/home/
return function(self, request, *args, **kwargs)
File "/home/
self.
File "/home/
exit_
File "/home/
serial=serial,
File "/usr/lib/
return getattr(
File "/usr/lib/
obj.
File "/home/
self.
File "/usr/lib/
raise ValidationError
django.
This was due to having a GPS watch plugged in which was showing itself as a disk of 978k in size.
Related branches
- Brendan Donegan (community): Approve
- Andres Rodriguez (community): Approve
-
Diff: 53 lines (+25/-0)2 files modifiedsrc/metadataserver/models/commissioningscript.py (+8/-0)
src/metadataserver/models/tests/test_commissioningscript.py (+17/-0)
summary: |
- Disks less than 4MB in size cause a traceback + Disks less than 4MB in size cause a traceback on the MAAS server |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
That disk should be skipped and not added to MAAS.