Ask Your Question

VM getting deployed in Overcloud Controller instead of Compute Host

asked 2019-10-19 07:13:11 -0500

Sheshadri23 gravatar image

Hello Stackers,

Recently i was testing Triple-o deployment (Pike) on HP servers , i manage to deploy all components under cloud, over cloud , compute host etc without any error. After VM creation i noticed that every time i create it will host on Controller rather than compute hosts 1,2 . since the controller host is already loaded with openstack services i am not able to test some features between hosts... Do we have any workaround to host VM on computes ?

Thanks in advance Sheshadri

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2019-10-19 08:15:44 -0500

You can temporarily disable compute services on the controller with openstack compute service set.

I suspect, however, that some misconfiguration prevents the compute nodes from receiving instances.

edit flag offensive delete link more


@Bernd baush : i have tried disabling computer service on controller and creating instance on compute got error "No valid host was found. There are not enough hosts available" even though i have enough space to launch the instances. is there any host to cell mapping needs to done on computer host ?

Sheshadri23 gravatar imageSheshadri23 ( 2019-10-30 02:23:36 -0500 )edit

You map a host to a cell by configuring the message queue and database servers to which it connects. I don't know how TripleO does that, and whether it supports multi-cell configuration. You are unlikely to have more than one cell.

In any case, cell mapping has nothing to do with your problem.

Bernd Bausch gravatar imageBernd Bausch ( 2019-10-30 07:28:57 -0500 )edit

Space is not the only criterion for selecting a compute node. Check the scheduler log for reasons why the hosts are considered unsuitable for running your instance. You may have to configure debug logging.

Bernd Bausch gravatar imageBernd Bausch ( 2019-10-30 07:31:34 -0500 )edit

Sorry to ask the obvious, but you have 'sourced' overcloudrc and not trying to depoy using the 'stackrc' (undercloud) credentials ?
Other things to check.. (again using . ~/overcloudrc) * openstack hypervisor list * check you hypervisor resources again the flavours

jkrah gravatar imagejkrah ( 2019-11-13 03:57:45 -0500 )edit

Get to know Ask OpenStack

Resources for moderators

Question Tools



Asked: 2019-10-19 07:13:11 -0500

Seen: 62 times

Last updated: Oct 19 '19