On Thu, 28 Mar 2019, Navdeep Uniyal wrote:
Hi Bharat,
Thank you very much. It worked for me. However, I am getting resource error while starting the cluster. I have enough resources available in the hypervisor, but it errors out:
faults | {'0': 'ResourceInError: resources[0].resources.kube-master: Went to status ERROR due to "Message: No valid host was found. , Code: 500"', 'kube_masters': 'ResourceInError: resources.kube_masters.resources[0].resources.kube-master: Went to status ERROR due to "Message: No valid host was found. , Code: 500"', 'kube-master': 'ResourceInError: resources.kube-master: Went to status ERROR due to "Message: No valid host was found. , Code: 500"'} |
Nova Scheduler Error:
2019-03-28 11:36:37.686 79522 ERROR nova.scheduler.client.report [req-82c4fb8b-785b-40bf-82fc-ff9d0e6101a0 b4727cb329c14c388d777d0ce38c8a6b 4c6bc4445c764249921a0a6e40b192dd - default default] Failed to retrieve allocation candidates from placement API for filters {'VCPU': 4, 'MEMORY_MB': 4096, 'DISK_GB': 80}. Got 500: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
You'll want to look in the logs for your placement service (perhaps nova-placement-api.log) or the apache2 general error.log to find out what's causing this 500. Until that's resolved you won't be able to land any VMs. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent