report_boot_images leaves a nice stack trace in maas.log
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Critical
|
Unassigned | ||
1.2 |
Invalid
|
Critical
|
Unassigned |
Bug Description
ERROR 2012-11-13 18:42:16,675 maas.maasserver #######
ERROR 2012-11-13 18:42:16,675 maas.maasserver Traceback (most recent call last):
File "/usr/lib/
response = callback(request, *callback_args, **callback_kwargs)
File "/usr/lib/
response = func(*args, **kwargs)
File "/usr/lib/
result = self.error_
File "/usr/lib/
result = meth(request, *args, **kwargs)
File "/usr/lib/
return function(self, request, *args, **kwargs)
File "/usr/lib/
images = json.loads(
File "/usr/lib/
return _default_
File "/usr/lib/
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/
raise JSONDecodeError("No JSON object could be decoded", s, idx)
JSONDecodeError: No JSON object could be decoded: line 1 column 0 (char 0)
Changed in maas: | |
status: | New → Triaged |
importance: | Undecided → Critical |
The precise package I was testing with was several revisions old. This is no longer a problem with the latest revision.