Comment 1 for bug 1219902

From @Aaron's duplicate

If the initial install failed, destroy-service does not work, but does not report that it isn't working.

$ juju destroy-service jenkins
$ juju status
...
services:
  jenkins:
    charm: local:precise/jenkins-2
    exposed: true
    life: dying
    units:
      jenkins/0:
        agent-state: error
        agent-state-info: 'hook failed: "install"'
        agent-version: 1.12.0
        life: dying
        machine: "1"
        public-address: 10.55.32.32

This went on until I destroyed the environment.

Later on, I determined that I could work around the issue by doing "juju resolve" first, before "juju destroy-service".