[2.0a4] Disks less than 4MB in size cause a traceback on the MAAS server

Bug #1580280 reported by Brendan Donegan
6
This bug affects 1 person
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/current <==
2016-05-10 17:42:00 [maasserver] ERROR: ################################ Exception: {'size': ['Ensure this value is greater than or equal to 4194304.']} ################################
2016-05-10 17:42:00 [maasserver] ERROR: Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/django/core/handlers/base.py", line 132, in get_response
    response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/home/brendand/src/maas/trunk/src/maasserver/utils/views.py", line 180, in view_atomic_with_post_commit_savepoint
    return view_atomic(*args, **kwargs)
  File "/usr/lib/python3.5/contextlib.py", line 30, in inner
    return func(*args, **kwds)
  File "/home/brendand/src/maas/trunk/src/maasserver/api/support.py", line 54, in __call__
    response = upcall(request, *args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/views/decorators/vary.py", line 21, in inner_func
    response = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/piston3/resource.py", line 190, in __call__
    result = self.error_handler(e, request, meth, em_format)
  File "/usr/lib/python3/dist-packages/piston3/resource.py", line 188, in __call__
    result = meth(request, *args, **kwargs)
  File "/home/brendand/src/maas/trunk/src/maasserver/api/support.py", line 235, in dispatch
    return function(self, request, *args, **kwargs)
  File "/home/brendand/src/maas/trunk/src/metadataserver/api.py", line 494, in signal
    self._store_commissioning_results(node, request)
  File "/home/brendand/src/maas/trunk/src/metadataserver/api.py", line 441, in _store_commissioning_results
    exit_status=script_result)
  File "/home/brendand/src/maas/trunk/src/metadataserver/models/commissioningscript.py", line 324, in update_node_physical_block_devices
    serial=serial,
  File "/usr/lib/python3/dist-packages/django/db/models/manager.py", line 127, in manager_method
    return getattr(self.get_queryset(), name)(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/django/db/models/query.py", line 348, in create
    obj.save(force_insert=True, using=self.db)
  File "/home/brendand/src/maas/trunk/src/maasserver/models/cleansave.py", line 28, in save
    self.full_clean()
  File "/usr/lib/python3/dist-packages/django/db/models/base.py", line 1171, in full_clean
    raise ValidationError(errors)
django.core.exceptions.ValidationError: {'size': ['Ensure this value is greater than or equal to 4194304.']}

This was due to having a GPS watch plugged in which was showing itself as a disk of 978k in size.

Tags: storage

Related branches

summary: - Disks less than 4MB in size cause a traceback
+ Disks less than 4MB in size cause a traceback on the MAAS server
Revision history for this message
Blake Rouse (blake-rouse) wrote : Re: Disks less than 4MB in size cause a traceback on the MAAS server

That disk should be skipped and not added to MAAS.

summary: - Disks less than 4MB in size cause a traceback on the MAAS server
+ [2.0a4] Disks less than 4MB in size cause a traceback on the MAAS server
tags: added: storage
Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 2.0.0
Revision history for this message
Lee Trager (ltrager) wrote :

Brendan, could you please verify the MP linked fixes your problem? I tested using a small loop back device but I don't have a GPS watch to verify with.

Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
status: Fix Committed → Fix Released
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.