Bug 851261
| Summary: | Status and Power status not updated after "os-stop" action | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Jaroslav Henner <jhenner> |
| Component: | python-django-horizon | Assignee: | Julie Pichon <jpichon> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Yaniv Kaul <ykaul> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 1.0 (Essex) | CC: | athomas, jkt |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-01-14 15:17:15 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Note that the server really shuts down -- virsh list gets empty and it disappears from virt-manager, but the power status is not updated. > 3. Observe status in dashboard
So is this a Dashboard issue, not Nova?
Please try with latest python-django-horizon-2012.2.1-2.el6ost Using Folsom / python-django-horizon-2012.2.1-2.el6ost, if I run the curl command in the description, the instance status and power state in the dashboard immediately switch to "shutoff" and "shutdown". |
Description of problem: Version-Release number of selected component (if applicable): Puddle Essex 2012-08-10.3 How reproducible: always Steps to Reproduce: 1. Have a server 2. Stop it using: echo '{"os-stop": null}' \ | curl -H 'accept: application/json' \ -H 'Content-Type: application/json' \ -H 'X-Auth-Token: e9de9e0863d3474b8b20d3078a7c35b7' \ --data @- \ 'http://nova-api.lithium:8774/v2/77ee297e46894491b6836119608b2b1c/servers/2d6c3405-c59e-4593-8736-56c0d033f611/action' 3. Observe status in dashboard Actual results: Status: Stopped, hourglass Power State: Running, after some time it switches to No State Expected results: Stopped, no hourglass, SHUTOFF Additional info: Severity high because it causes long waiting for timeout in Tempest tests