stopped instance in EC2 always considered "running"

[Tim Penhey]

After stopping one of the machines using a method outside of Juju, the instance poller fails to change the instance status:

2015-11-25 23:04:39 WARNING juju.worker.instanceupdater updater.go:251 cannot get instance info for instance "i-933f5123": instance i-933f5123 not found

The error is logged, then ignored, and the status is never updated.

[Anastasia (anastasia-macmood)]

I am pretty sure that this has been fixed.
I was re-running similar scenario for bug # 1453096:
1. bootstrap on AWS
2. deploy couple of ubuntu units
3. stop one of the unit machines through AWS EC2 API
4. watch juju status

Once machine is stopped, the status correctly reports it as "down".

[Anastasia (anastasia-macmood)]

Explicitly mentioning that even though I am putting this bug on 2.1-rc1 milestone, the fix went in into one of the previous releases. None of the released milestones are available in launchpad for selection. Consequently, I am targeting it to our current milestone.