exceptions.ValueError: No JSON object could be decoded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
Critical
|
Unassigned | ||
simplestreams |
Invalid
|
Undecided
|
Unassigned |
Bug Description
==> /var/log/
2015-05-21 12:01:12-0400 [-] Unhandled error in Deferred:
2015-05-21 12:01:12-0400 [-] Unhandled Error
Traceback (most recent call last):
File "/usr/lib/
self.
File "/usr/lib/
self.run()
File "/usr/lib/
self.
--- <exception caught here> ---
File "/usr/lib/
result = context.call(ctx, function, *args, **kwargs)
File "/usr/lib/
return self.currentCon
File "/usr/lib/
return func(*args,**kw)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
boot_
File "/usr/lib/
image_
File "/usr/lib/
source['url'], keyring=
File "/usr/lib/
dumper.
File "/usr/lib/
return self.sync_
File "/usr/lib/
self.
File "/usr/lib/
data = util.load_
File "/usr/lib/
return json.loads(content)
File "/usr/lib/
return _default_
File "/usr/lib/
obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/
raise ValueError("No JSON object could be decoded")
exceptions.
MAAS cluster that was working just fine, with trusty previously imported. I did this:
1. Changed streasm URL from releases to daily.
2. Selected 15.10 (willy) and tried to import.
3. Region imported the image
4. Cluster stayed in out-of-sync and did not start the import.
5. I had to manually try to improt images from the webui again. After a while cluster started import.
Changed in maas: | |
milestone: | none → 1.8.0 |
importance: | Undecided → Critical |
Changed in maas: | |
assignee: | nobody → Mike Pontillo (mpontillo) |
Changed in simplestreams: | |
status: | New → Incomplete |
Changed in maas: | |
status: | Incomplete → Invalid |
Changed in simplestreams: | |
status: | Incomplete → Invalid |
Changed in maas: | |
assignee: | Mike Pontillo (mpontillo) → nobody |
I haven't been able to reproduce this. Are there any special conditions on the cluster server? Are you still seeing the issue? Can we take a look at the server?
I did see similar problems when I was working on the MAAS+Snappy demo, but the disk image was too small. (We seem to handle things *very* poorly when we run out of disk space.)
At this point, I think it looks like the problem is not necessarily in MAAS code. I recommend adding more testing around the python- simplestreams upstream code to address corner cases like this.