Succeed message for Resize Instance is confusing (resize is async operation)
Bug #1277257 reported by
Cindy Lu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard (Horizon) |
Fix Released
|
Wishlist
|
Ana Malagon |
Bug Description
If I try to size up a flavor (m1.xlarge), it gives me the message "Success: Preparing instance "____" for resize" - but nothing happens.
Please see the attached image.
The top image shows a successful resize. The second shows the successful message, but no behavior.
Changed in horizon: | |
assignee: | nobody → Ana Malagon (atmalagon) |
summary: |
- Resize Instance doesn't work + Succeed message for Resize Instance is confusing (resize is async + operation) |
Changed in horizon: | |
milestone: | none → icehouse-rc1 |
Changed in horizon: | |
status: | Fix Committed → Fix Released |
Changed in horizon: | |
milestone: | icehouse-rc1 → 2014.1 |
To post a comment you must log in.
It seems like Resize is an asynchronous function and that is why we don't get a result immediately (and I'm guessing we try to indicate so by saying "Preparing" rather than "Resized successfully" or something like that). All we can confirm is that we sent the request to Nova.
REQ: curl -i 'http:// 192.168. 100.177: 8774/v2/ 42365c9f445a46e 791e62d9093c113 ad/servers/ 53f67c2d- 4724-419b- 896c-0ddb1a9d65 25/action' -X POST -H "X-Auth-Project-Id: 42365c9f445a46e 791e62d9093c113 ad" -H "User-Agent: python-novaclient" -H "Content-Type: application/json" -H "Accept: application/json" -H "X-Auth-Token: 83edcf42258c48c 7119ba8b1b584d6 3e" -d '{"resize": {"flavorRef": "5"}}' Dict({' date': 'Fri, 07 Feb 2014 16:51:36 GMT', 'content-length': '0', 'content-type': 'text/html; charset=UTF-8', 'x-compute- request- id': 'req-0d62ed35- 8108-40ef- 84e8-96d51760b6 ab'})
RESP: [202] CaseInsensitive
The behaviour for Nova client is similar if I try to resize to a flavour too large for my VM:
$ nova resize 53f67c2d- 4724-419b- 896c-0ddb1a9d65 25 5
$
In the nova-conductor logs:
WARNING nova.scheduler. utils [req-9a544a50- 2bf4-4c58- aafa-a1b3b57b11 d4 demo demo] Failed to compute_ task_migrate_ server: No valid host was found.
I don't see a way for Horizon to surface the error, or perhaps there is a message we can consume once the real time communication blueprint is implemented? ( https:/ /blueprints. launchpad. net/horizon/ +spec/realtime- communication ) Instance actions list the request ids but not the results either, as far as I can tell.