juju status showing charm unit in error state but getting "ERROR unit is not in an error state" message when resolving charm

[Bilal Baqar]

juju status showing a unit of nova-compute charm in an error state right after the unit was rebooted.

resolving the charm unit using [juju resolved --retry nova-compute/1] gives the error message:
"ERROR unit "nova-compute/1" is not in an error state"

-output of juju status --format=tabular
http://paste.ubuntu.com/18277002/

-output of juju status
http://paste.ubuntu.com/18277015/

-juju logs of the nova-compute/1 unit
http://paste.ubuntu.com/18278303/

-juju machine log
http://paste.ubuntu.com/18278291/

[Bilal Baqar (bbaqar)]

juju-core version is 1.25.5

[Cheryl Jennings (cherylj)]

It would be interesting to see what the status is in the DB. Are you able to install the mongo client on the state server? If so, could you run the following and attach the output?

1 - Install the mongodb-clients package on the state server:
    `sudo apt-get install mongodb-clients`

2 - Connect to mongo on the state server:
    `mongo --ssl -u admin -p $(sudo grep oldpassword /var/lib/juju/agents/machine-0/agent.conf | awk -e '{print $2}') localhost:37017/admin`

3 - Query the status collection for status on nova-compute. You'll need to 'use juju', then query the statuses collection:

MongoDB shell version: 2.6.10
connecting to: localhost:37017/admin
juju:PRIMARY> use juju
switched to db juju
juju:PRIMARY> db.statuses.find({_id:{ $regex: '.*nova-compute.*'}}).pretty()

[Bilal Baqar (bbaqar)]

Output of the above command: http://paste.ubuntu.com/18806295/

[Anastasia (anastasia-macmood)]

This looks like a symptom of Juju overwriting status set explicitly by workload as described in bug # 1597481. I am marking this as a duplicate.