import flow doesn't raise error on forbidden location
Bug #1495519 reported by
Flavio Percoco
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Medium
|
wangxiyuan | ||
Liberty |
New
|
Medium
|
Unassigned |
Bug Description
The following command correctly raises an exception server side but it doesn't report the error back to the user. This ends up in the user "thinking" the task was created correctly:
$ glance --os-image-
Changed in glance: | |
importance: | Undecided → High |
Changed in glance: | |
status: | New → In Progress |
Changed in glance: | |
importance: | High → Medium |
Changed in glance: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hi, Flavio, I submit a bug before ,it's related to this bug.
https:/ /bugs.launchpad .net/glance/ +bug/1488311
https:/ /review. openstack. org/#/c/ 216555/
The reason is that glance only checked the parameters before taskflow start, but didn't do any dispose about task status.
As in taskflow, it has checked the parameters already, we could remove the checking before the taskflow.