我在安装了OpenStack的VMware中有一个VM。 OpenStack有两个实例（2GB，1VCPU和4GB，4VCPU）。我将具有4GB，4VCPU的实例之一的大小更改为使用NOVA大小的8 GB，并且起作用。现在，我需要RAM至少16 GB和VCPUS 6，但是调整命令的完成（秒内）未能产生错误和RAM大小尚未升级。
我终于在Nova-conductor.log中发现了以下错误，
nova.exception.NoValidHost: No valid host was found.
: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 10:57:11.622 56 WARNING nova.scheduler.utils [req-31c98f42-d465-4773-9b4a-3474aef85a1c 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] [instance: 7b0e27e4-8c78-4dc5-bf38-3cfc02d356d8] Setting instance to ACTIVE state.: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 11:01:46.757 55 WARNING nova.scheduler.utils [req-cfa535cc-c19f-4b75-8fde-224d8f3610d5 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] Failed to compute_task_migrate_server: No valid host was found.
Traceback (most recent call last):
File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_messaging/rpc/server.py", line 241, in inner
return func(*args, **kwargs)
File "/var/lib/kolla/venv/lib/python3.8/site-packages/nova/scheduler/manager.py", line 209, in select_destinations
raise exception.NoValidHost(reason="")
nova.exception.NoValidHost: No valid host was found.
: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 11:01:46.759 55 WARNING nova.scheduler.utils [req-cfa535cc-c19f-4b75-8fde-224d8f3610d5 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] [instance: 7b0e27e4-8c78-4dc5-bf38-3cfc02d356d8] Setting instance to ACTIVE state.: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
我已经阅读了一些文章，这些文章会更改 ram_allocation_ratio 和 cpu_allocation_ratio 会起作用，但我不知道我应该确切地在我的身上更改它案件。我的VM部署OpenStack的VM具有 25 GB RAM和16个处理器核心，而主机机器具有 32 GB RAM和32个逻辑处理器（16个内核）。如何修改这些变量，还是我缺少其他东西？
编辑：
我能够通过分析 OpenStack Hypervisor统计信息显示的输出来解决问题。我用来扩展尺寸的风味需要更多的磁盘空间（80克），而不是在管理程序统计数据中显示的磁盘空间（47G）。通过扩展VM的大小，然后扩展Directory /var/lib （由于我正在使用Docker样式部署），问题已解决。
I have got a VM in VMware on which openstack is installed. Openstack has two instances (2GB,1VCPU and 4GB,4VCPU). I changed the size of one of the instance having 4GB, 4VCPU to 8 GB using nova resize and it worked. Now I need RAM atleast 16 GB and VCPUs 6 but the resize command finishes way too early (within seconds) without generating error and RAM size has not upgraded.
I finally found following error in nova-conductor.log
nova.exception.NoValidHost: No valid host was found.
: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 10:57:11.622 56 WARNING nova.scheduler.utils [req-31c98f42-d465-4773-9b4a-3474aef85a1c 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] [instance: 7b0e27e4-8c78-4dc5-bf38-3cfc02d356d8] Setting instance to ACTIVE state.: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 11:01:46.757 55 WARNING nova.scheduler.utils [req-cfa535cc-c19f-4b75-8fde-224d8f3610d5 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] Failed to compute_task_migrate_server: No valid host was found.
Traceback (most recent call last):
File "/var/lib/kolla/venv/lib/python3.8/site-packages/oslo_messaging/rpc/server.py", line 241, in inner
return func(*args, **kwargs)
File "/var/lib/kolla/venv/lib/python3.8/site-packages/nova/scheduler/manager.py", line 209, in select_destinations
raise exception.NoValidHost(reason="")
nova.exception.NoValidHost: No valid host was found.
: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
2022-05-09 11:01:46.759 55 WARNING nova.scheduler.utils [req-cfa535cc-c19f-4b75-8fde-224d8f3610d5 10f23c55b2ce420aa1e757062f3874f8 c458f62c51d249ef9bf2b9f11c4ddb98 - default default] [instance: 7b0e27e4-8c78-4dc5-bf38-3cfc02d356d8] Setting instance to ACTIVE state.: nova.exception_Remote.NoValidHost_Remote: No valid host was found.
I have read in some articles that changing ram_allocation_ratio and cpu_allocation_ratio will work but I dont know exactly how I should change it in my case. My VM where openstack is deployed has 25 GB Ram and 16 processor cores while the host machine has 32 GB RAM and 32 logical processors (16 cores). How can I modify these variables or is there something else I am missing?
EDIT:
I was able to solve the problem by analyzing the output of openstack hypervisor stats show. The flavor I was using to extend the size was demanding more disk space (80G) then the one showed in hypervisor stats (47G). By extending the size of VM and then directory /var/lib (since i am using docker style deployment), the issue resolved.
发布评论
评论（1）
您是否在 nova.conf 中设置了
recerved_host_memory_mb？您已部署的
OpenStack的版本是什么？默认
ram_allocation_ratiois 1.5 ，您可以将其设置为 2 或更多，然后检查错误是否找到有效的主机。修复。这是示例配置文件。通过
OpenStack Hypervisor统计信息显示，获取您的管理程序统计信息详细信息。确保系统资源充分，也许在您的环境中有一些限制，例如端口， disk 或其他磁盘。其他引用的更新参考：
根本原因是 strage 创建实例具有磁盘容量 80G ，但仅获取
free_disk_gbis 47Hypervisor Stats。并通过扩展主机（管理程序）的磁盘容量来修复它。Have you set the
reserved_host_memory_mbin nova.conf?What's the version about your deployed
openstack?The default
ram_allocation_ratiois 1.5, and you could set it to 2 or more, then check whether the errorNo valid host was found.fixed or not. This is the Sample Configuration File.Get your hypervisor stats details by
openstack hypervisor stats show. Make sure that system resource sufficiently, maybe there is some limit in your environment such as ports, disk or others.Update for others reference:
The root cause is that the flavor with which instance was created has disk capacity 80G, but only get
free_disk_gbis 47 byhypervisor stats. And OP fixed it by extend the host(hypervisor)'s disk capacity.