Bug 1020506
Summary: | openstack-nova: the creation of instance with a used bootable volume should fail | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Yogev Rabl <yrabl> |
Component: | openstack-nova | Assignee: | RHOS Maint <rhos-maint> |
Status: | CLOSED NOTABUG | QA Contact: | Ami Jeain <ajeain> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.0 | CC: | hateya, ndipanov, yeylon |
Target Milestone: | --- | ||
Target Release: | 4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-10-17 21:00:19 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: |
Description
Yogev Rabl
2013-10-17 19:29:24 UTC
This is expected behavior. Server creation is an async operation. As long as the input passes initial sanity checks, there are a bunch of ways that it may fail and result in being put in an ERROR state. Even if we did do this check on the API side, it wouldn't catch all cases. There is a bit of a race condition here if two such requests came in at the same time. |