yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02043
[Bug 1161935] Re: Exceeding fixed_ip quota does not result in instance being set to error state
** Changed in: nova
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1161935
Title:
Exceeding fixed_ip quota does not result in instance being set to
error state
Status in OpenStack Compute (Nova):
Invalid
Bug description:
Expected:
When boot of a nova instance fails due to exceeding "fixed_ip" quota,
the instance should be set to "ERROR" state, and `nova show $instance_name`
should inform the client the reason for the error.
Actual:
When boot of a nova instance fails due to exceeding "fixed_ip" quota,
the instance becomes stuck in "BUILD" state, and the only indication
of what has happens is in nova logs (error is not visible client-side)
Repro:
- Install latest nova from trunk
- Boot 11 instances - the 11th will become stuck in "BUILD"
Affected Versions:
- Recent revisions of nova trunk, since fixed_ip quota was added.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1161935/+subscriptions