ar.vaze=nttdata....@lists.launchpad.net] On Behalf
>> Of Jay Pipes
>> Sent: Wednesday, May 30, 2012 12:58 AM
>> To: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
>> space fail to spawn
>>
>> Leander, I wo
=nttdata@lists.launchpad.net] On Behalf
>> Of Jay Pipes
>> Sent: Wednesday, May 30, 2012 12:58 AM
>> To: openstack@lists.launchpad.net
>> Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
>> space fail to spawn
>>
>> Leander, I would su
@lists.launchpad.net[mailto:
> openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net] On Behalf
> Of Jay Pipes
> Sent: Wednesday, May 30, 2012 12:58 AM
> To: openstack@lists.launchpad.net
> Subject: Re: [Openstack] [Nova] Instances which use flavors with disk
> space
30, 2012 12:58 AM
To: openstack@lists.launchpad.net
Subject: Re: [Openstack] [Nova] Instances which use flavors with disk space
fail to spawn
Leander, I would submit a bug about this. The error message is cryptic (to say
the least!) and I think it would be better if the scheduler determined
Leander, I would submit a bug about this. The error message is cryptic
(to say the least!) and I think it would be better if the scheduler
determined if the flavor requested has a memory request greater than the
total amount available on the server! I'm a bit disappointed that the
request even
For anyone interested, i've figured out that the instances were not getting
spawned because the amount of memory in the flavor was equal to the maximum
memory available through the underlying hardware.
On Tue, May 29, 2012 at 11:10 AM, Leander Bessa Beernaert <
leande...@gmail.com> wrote:
> Hello
Hello,
I'm unable to boot any image with a flavor that has a disk space associated
with it. It always fails at the spawning state. Below it the log output of
nova-compute:
2012-05-28 16:20:25 ERROR nova.compute.manager
>> [req-1c725f9c-acae-47c4-b5ae-9ed5d2d9830c 9494d025721c4d7bb28a16fa796f9414
7 matches
Mail list logo
