mojo reports no status errors despite errors existing then it hangs

I ran a mojo manifest on wendigo to upgrade my staging environment, and mojo stalled for over an hour waiting for the environment to reach a steady state.

Before waiting for a steady state, mojo checked juju status and did not report any problems, but checking status by hands shows some units in a failed state.

full juju status and the output from the manifest are here:

https://private-fileshare.canonical.com/~codersquid/mojo_steady/

mojo snippet

#############################################################################
Check juju status before starting upgrade
#############################################################################

2017-12-06 19:24:39 [INFO] Checking Juju status
2017-12-06 19:24:40 [INFO] No statuses are in a bad state
2017-12-06 19:24:40 [INFO] Statuses are in a stable state
2017-12-06 19:24:40 [INFO] No statuses are in a bad state
2017-12-06 19:24:40 [INFO] Statuses are in a stable state
2017-12-06 19:24:40 [INFO] No statuses are in a bad state
2017-12-06 19:24:40 [INFO] Statuses are in a stable state
2017-12-06 19:24:40 [INFO] Services
   Agent State
    started: 47
2017-12-06 19:24:40 [INFO] Machines
   Instance State
    ACTIVE: 11
2017-12-06 19:24:40 [INFO] Machines
   Agent State
    started: 11
2017-12-06 19:24:40 [INFO] Waiting for environment to reach steady state

juju status snippet

    cert-postgresql/0:
        workload-status:
          current: active
          message: Live master
          since: 13 Nov 2017 11:47:30Z
        agent-status:
          current: failed
          message: accept leadership
          since: 06 Dec 2017 20:26:27Z
          version: 1.25.3
        agent-state: started
        agent-version: 1.25.3
        machine: "9"
        open-ports:
        - 5432/tcp