No JSON object could be decoded on juju-check-wait

Bug #1644836 reported by Matthew Williams
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Juju Wait Plugin
Fix Released
Medium
Stuart Bishop
Mojo: Continuous Delivery for Juju
Fix Released
Undecided
Stuart Bishop

Bug Description

Whilst deploying a previously working mojo spec I get the following error:

2016-11-25 13:22:18 [INFO] Waiting for environment to reach steady state
2016-11-25 13:22:58 [INFO] All units idle since 2016-11-25 13:22:39.202414Z (prometheus/1, ubuntu-basenode/0)
2016-11-25 13:23:07 [ERROR] Unknown error
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/mojo/cli.py", line 583, in run_with_args
    args.func(args)
  File "/usr/lib/python2.7/dist-packages/mojo/utils.py", line 305, in wrapped
    return method(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/mojo/cli.py", line 312, in run_from_manifest
    manifest.run(project, workspace, args.stage)
  File "/usr/lib/python2.7/dist-packages/mojo/manifest.py", line 94, in run
    phase_name.run(project, workspace, stage)
  File "/usr/lib/python2.7/dist-packages/mojo/phase.py", line 955, in run
    juju_status.check_and_wait(timeout=status_timeout, wait_for_steady=True)
  File "/usr/lib/python2.7/dist-packages/mojo/juju/status.py", line 188, in check_and_wait
    wait()
  File "/usr/lib/python2.7/dist-packages/mojo/juju/wait.py", line 416, in wait
    uname for uname, leader in unit_leadership.items()
  File "/usr/lib/python2.7/dist-packages/mojo/juju/wait.py", line 130, in leadership_poll
    unit_map[unit] = json.loads(stdout)
  File "/usr/lib/python2.7/json/__init__.py", line 338, in loads
    return _default_decoder.decode(s)
  File "/usr/lib/python2.7/json/decoder.py", line 366, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/usr/lib/python2.7/json/decoder.py", line 384, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded

All units appear to be active with no errors.

Using juju 1.24.7

Related branches

Revision history for this message
Stuart Bishop (stub) wrote :

This error occurs when 'juju run' fails, but returns a success code. This has been seen to happen in situations like out of memory, disk space on the unit. While this is a juju bug, it won't be fixed for 1.24.7. Best I can do is catch the error and report the unit as failed.

Stuart Bishop (stub)
Changed in juju-wait:
status: New → Triaged
importance: Undecided → Medium
Stuart Bishop (stub)
Changed in juju-wait:
status: Triaged → Fix Committed
assignee: nobody → Stuart Bishop (stub)
Revision history for this message
Nick Moffitt (nick-moffitt) wrote :

This just hit again while working on RT#97979

Stuart Bishop (stub)
Changed in mojo:
status: New → In Progress
assignee: nobody → Stuart Bishop (stub)
Stuart Bishop (stub)
Changed in juju-wait:
status: Fix Committed → Fix Released
Tom Haddon (mthaddon)
Changed in mojo:
status: In Progress → Fix Committed
Tom Haddon (mthaddon)
Changed in mojo:
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.