stopped instance in EC2 always considered "running"
Bug #1520373 reported by
Tim Penhey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Unassigned |
Bug Description
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.
The error is logged, then ignored, and the status is never updated.
summary: |
- stopped instance in EC2 always considered "started" + stopped instance in EC2 always considered "running" |
Changed in juju-core: | |
milestone: | 1.26-alpha3 → 2.0-alpha2 |
Changed in juju-core: | |
milestone: | 2.0-alpha2 → 2.0-alpha3 |
Changed in juju-core: | |
milestone: | 2.0-alpha3 → 2.0-beta4 |
Changed in juju-core: | |
milestone: | 2.0-beta4 → 2.1.0 |
affects: | juju-core → juju |
Changed in juju: | |
milestone: | 2.1.0 → none |
milestone: | none → 2.1.0 |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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".