openstack team mailing list archive

[Belmiro Moreira <moreira.belmiro.email.lists@xxxxxxxxx>]

Hi,
Let me just had that an instance can fail in different filters in different hosts.
Some filters LOG the reason if debug=true.
Check /var/log/nova/scheduler.log

cheers,
Belmiro
 
On May 21, 2013, at 3:18 PM, Lei Zhang <redheadflyundershadow@xxxxxxxxx> wrote:

> Yes, nova-scheduler has lots of filters to check if nova-compute node fit the requirement of the instance you wanna launch.
> Like availability-zone filter, RAM filter, cpu core filter, etc. If all the compute node failed to pass those filters, it raise this exception.
> 
> Regards
> Lei
> 
> 
> On Tue, May 21, 2013 at 4:13 AM, Aaron Rosen <arosen@xxxxxxxxxx> wrote:
> Usually means that the instance trying to be launched can't be scheduled to any nova-compute nodes. The log message should include a reason why though. 
> 
> 
> 
> 
> On Mon, May 20, 2013 at 12:06 PM, Remo Mattei <remo@xxxxxxxxxx> wrote:
> Hello everyone, 
> 
> I wonder if someone can give me a more detail overview about the raise exception.NoValidHost
> on what does raise mean. 
> 
> Thanks
> Remo 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp