wedged unit state error but can't be resolved

[Kapil Thangavelu]

$ juju-status snippet

  cache-lb:
    charm: local:precise/haproxy-42
    exposed: false
    relations:
      reverseproxy:
      - wordpress
    units:
      cache-lb/0:
        agent-state: error
        agent-state-info: 'hook failed: "relation-changed"'
        agent-version: 1.10.0
        machine: "6"
        public-address: ec2-184-72-139-129.compute-1.amazonaws.com

$ juju resolved cache-lb/0
  error: cannot set resolved mode for unit "cache-lb/0": already resolved

I was trying some automated resolved retry logic in deployer as can be seen in the unit log, but after a few retries it gets wedged.

http://paste.ubuntu.com/5621395/

incidentally the rel hook error is due to the lack of -r support (reported separately).

[William Reade (fwereade)]

Next time you encounter this, please report back what happens if you ssh to the machine and bounce the unit agent process (something like `sudo restart jujud-unit-cache-lb-0`). If this resolves the issue, it should eliminate the possibility of serious state brokenness and isolate it to the unit agent itself.