Hi Leslie, I've checked the log in the compute nodes and the error is related to the bridge:
^[[01;31m2016-07-20 23:30:44.470 TRACE nova.compute.manager ^[[01;35m[instance: dcf75116-fcaa-4f43-bac0-f93bc1fcaa9a] ^[[00mlibvirtError: Cannot get interface MTU on 'br-int': No such device But ovs-vsctl show tells me that the bridge in created. I think it's related to that. Thanks 2016-07-23 19:27 GMT+02:00 Leslie-Alexandre DENIS <cont...@ladenis.fr>: > Hello, > > to clarify, the nova-scheduler is just saying that the boot process > can't succeed because none of your registered computes fit, or there is > none at all (from scheduler pov). > > First thing first: > > - flavor specs ? > - do the computes register correctly their resources ? (check that in > nova-compute logs) > - are you using aggregates ? > - you should enable the debug/verbose mode on the controller and read > the nova-scheduler log in detail > > Regards. > > > _______________________________________________ > Mailing list: > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > > -- Silvia Fichera
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
