问题[openstack](server)

我对 openstack 不是很熟悉。我的 openstack 环境有两个控制器，我遇到了两个问题。

1. 当我检查状态时，更多主机处于关闭状态（但它们仍处于启动和运行状态，并且虚拟机正在其上运行）：

$ openstack compute service list --service nova-compute
+--------------------------------------+--------------+------------+-----------+----------+-------+----------------------------+
| ID                                   | Binary       | Host       | Zone      | Status   | State | Updated At                 |
+--------------------------------------+--------------+------------+-----------+----------+-------+----------------------------+
| 1b85d869-8cf3-42e9-86eb-************ | nova-compute | compute01  | nova      | enabled  | down  | 2025-03-03T12:20:14.000000 |
| f784d63b-cfb7-4425-af85-************ | nova-compute | compute02  | nova      | enabled  | down  | 2025-03-03T12:20:54.000000 |
| 3d051f6f-84cb-4e4b-9e64-************ | nova-compute | compute03  | nova      | enabled  | down  | 2023-05-07T04:03:10.000000 |
| 0e3b5f5a-591b-4a63-b21a-************ | nova-compute | compute04  | nova      | enabled  | down  | 2025-03-04T10:37:46.000000 |
| e10a28e8-f359-4a00-a5db-************ | nova-compute | compute05  | nova      | enabled  | down  | 2025-02-28T14:25:03.000000 |
| 67386517-0485-43ee-83b3-************ | nova-compute | compute08  | nova      | enabled  | up    | 2025-03-07T14:06:24.000000 |
| 2b19451c-e9af-4b23-aeff-************ | nova-compute | compute09  | nova      | disabled | down  | 2021-11-19T03:55:34.000000 |
| 0a0ba906-e96d-4ac3-9a65-************ | nova-compute | compute06  | nova      | enabled  | down  | 2025-02-28T12:14:33.000000 |
| 07a27e91-f8ce-4a58-8c0a-************ | nova-compute | compute10  | nova      | enabled  | down  | 2025-03-03T10:51:21.000000 |
| 3cc2b99c-f68f-4565-a422-************ | nova-compute | compute07  | nova      | enabled  | up    | 2025-03-07T14:06:15.000000 |
| 861011c4-09e5-4812-b26f-************ | nova-compute | compute11  | nova      | enabled  | up    | 2025-03-07T14:06:17.000000 |
| 75c32a27-8dfc-4236-b7d9-************ | nova-compute | compute12  | nova      | enabled  | up    | 2025-03-07T14:06:21.000000 |
| 0e37eaad-3285-4e56-a1d6-************ | nova-compute | compute25  | rack1     | enabled  | up    | 2025-03-07T14:06:20.000000 |
| 6fcfb08f-3f38-4d82-9bb8-************ | nova-compute | compute26  | rack1     | enabled  | up    | 2025-03-07T14:06:23.000000 |
| 8d680d2a-3c1f-443a-a43f-************ | nova-compute | compute29  | rack1     | disabled | down  | 2021-11-16T13:45:56.000000 |
| 6b95b193-e66e-47f3-9e28-************ | nova-compute | compute30  | rack1     | enabled  | up    | 2025-03-07T14:06:16.000000 |
| 2f921cc2-2e54-4263-b1e6-************ | nova-compute | compute31  | rack1     | enabled  | up    | 2025-03-07T14:06:20.000000 |
| e38b9ba2-01a0-46f8-a314-************ | nova-compute | compute32  | rack1     | enabled  | up    | 2025-03-07T14:06:17.000000 |
| 1c3162cb-3c56-4678-89d2-************ | nova-compute | compute33  | rack1     | enabled  | up    | 2025-03-07T14:06:15.000000 |
| 31e351fa-0012-4ca1-95ed-************ | nova-compute | compute24  | rack1     | enabled  | up    | 2025-03-07T14:06:16.000000 |
| 32e0b6ca-0c57-4d18-863c-************ | nova-compute | compute27  | rack1     | enabled  | up    | 2025-03-07T14:06:17.000000 |
| 887fc96c-8bc8-4f05-bada-************ | nova-compute | compute13  | AZ1       | enabled  | up    | 2025-03-07T14:06:15.000000 |
| 648a6a1d-2f09-4b5a-ac99-************ | nova-compute | compute14  | AZ1       | enabled  | up    | 2025-03-07T14:06:22.000000 |
| 3da7c060-0f65-4e2e-9ef0-************ | nova-compute | compute16  | AZ1       | enabled  | up    | 2025-03-07T14:06:17.000000 |
| a15b9200-0b80-477c-b98e-************ | nova-compute | compute17  | AZ1       | enabled  | up    | 2025-03-07T14:06:23.000000 |
| ef2066f6-6523-4781-86a3-************ | nova-compute | compute18  | AZ1       | enabled  | up    | 2025-03-07T14:06:23.000000 |
| cb38112a-9234-48da-9115-************ | nova-compute | compute19  | AZ1       | enabled  | up    | 2025-03-07T14:06:22.000000 |
| a13e86d5-114a-4145-a4d5-************ | nova-compute | compute20  | AZ1       | enabled  | up    | 2025-03-07T14:06:19.000000 |
| 91001b0f-7ce4-43d8-98fc-************ | nova-compute | compute21  | AZ1       | enabled  | up    | 2025-03-07T14:06:19.000000 |
| d62cecbb-d556-456d-b363-************ | nova-compute | compute22  | AZ1       | enabled  | up    | 2025-03-07T14:06:16.000000 |
| a5efa587-5a69-4d3b-b3b3-************ | nova-compute | compute23  | AZ1       | enabled  | up    | 2025-03-07T14:06:22.000000 |
| a820cfff-ffca-4b33-8921-************ | nova-compute | compute34  | AZ1       | enabled  | up    | 2025-03-07T14:06:15.000000 |
| 3c86c385-97c0-40e0-a139-************ | nova-compute | compute36b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:13.000000 |
| ca3f1243-d84d-4871-a476-************ | nova-compute | compute37b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:17.000000 |
| 5fd36263-d095-4d1c-b92d-************ | nova-compute | compute35b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:22.000000 |
| d2ae6fcb-abc0-4500-9e64-************ | nova-compute | compute39b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:19.000000 |
| 9797d22f-9d11-44b5-adb6-************ | nova-compute | compute40b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:18.000000 |
| b1809339-bfd3-4b84-99b8-************ | nova-compute | compute38b | AZ-PP     | enabled  | up    | 2025-03-07T14:06:15.000000 |
+--------------------------------------+--------------+------------+-----------+----------+-------+----------------------------+

这导致我无法部署新的虚拟机，因为我收到错误：

Error: Failed to perform requested operation on instance "  test.ts1.mydomain.com", the instance has an error status: Please try again later [Error: No valid host was found. There are not enough hosts available.]. 

2. 我可以通过 GUI 管理虚拟机，如果我尝试重建服务器，它仍然处于待处理状态

从控制器中我看到这些错误：

2025-03-07 14:16:51.448 3868 ERROR oslo.messaging._drivers.impl_rabbit [req-98ac1001-ba76-4cb6-bfca-be2efa0a3b9e 045df8a7fcf241e78f527994d5a77a9b 3c14771e53de4a2f80e138bd5df3bf5e - default default] [f1269656-782a-4418-8d59-d29d526a075d] AMQP server on controller.iaas.isp.dev:5672 is unreachable: Server unexpectedly closed connection. Trying again in 1 seconds.: OSError: Server unexpectedly closed connection
2025-03-07 14:16:52.471 3868 INFO oslo.messaging._drivers.impl_rabbit [req-98ac1001-ba76-4cb6-bfca-be2efa0a3b9e 045df8a7fcf241e78f527994d5a77a9b 3c14771e53de4a2f80e138bd5df3bf5e - default default] [f1269656-782a-4418-8d59-d29d526a075d] Reconnected to AMQP server on controller.iaas.isp.dev:5672 via [amqp] client with port 39944.

我尝试重新启动rabbitmq-server.service并重启控制器但问题并未解决。

直到几天前它还正常工作，有什么想法可以解决它吗？

我不知道如何进一步排除此故障。希望能得到帮助。

当我使用以下方式删除计算服务时：openstack compute service delete a04910ef-1441-4949-8ffb-6393c22141b2，我可以使用nova-compute以下方式在机器上重新启动sudo systemctl restart nova-compute以恢复 openstack 中的服务。

但是，该节点不再在openstack hypervisor list（例如在我的情况下为os-compute03.maas ）中列出：

$ openstack compute service list --service nova-compute
+--------------------------------------+--------------+-------------------+------+----------+-------+----------------------------+
| ID                                   | Binary       | Host              | Zone | Status   | State | Updated At                 |
+--------------------------------------+--------------+-------------------+------+----------+-------+----------------------------+
| d1fadd40-6035-4f76-b8c1-5b981d003832 | nova-compute | os-compute08.maas | nova | disabled | down  | 2024-09-25T14:02:55.000000 |
| 7e02a0bd-0e53-45bc-9680-99a33d98c05b | nova-compute | os-compute04.maas | nova | enabled  | up    | 2024-10-18T11:43:12.000000 |
| 7f47d65e-b041-44dc-927e-085effdf0ec9 | nova-compute | os-compute09.maas | nova | enabled  | up    | 2024-10-18T11:43:07.000000 |
| 3a7527b3-3664-4ae1-ac90-ac04e835ee5b | nova-compute | os-compute03.maas | nova | enabled  | up    | 2024-10-18T11:43:13.000000 |
+--------------------------------------+--------------+-------------------+------+----------+-------+----------------------------+

$ openstack hypervisor list
+----+---------------------+-----------------+----------+-------+
| ID | Hypervisor Hostname | Hypervisor Type | Host IP  | State |
+----+---------------------+-----------------+----------+-------+
|  1 | os-compute08.maas   | QEMU            | 10.0.1.8 | down  |
|  2 | os-compute04.maas   | QEMU            | 10.0.1.4 | up    |
|  3 | os-compute09.maas   | QEMU            | 10.0.1.9 | up    |
+----+---------------------+-----------------+----------+-------+

^ 没有os-compute03.maas

$ sudo nova-manage cell_v2 list_hosts
                                                                                                                                     
Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
Deprecated: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT".
+-----------+--------------------------------------+-------------------+
| Cell Name |              Cell UUID               |      Hostname     |
+-----------+--------------------------------------+-------------------+
|   cell1   | d3dfd353-b4ee-4293-b362-1e0175ebe337 | os-compute04.maas |
|   cell1   | d3dfd353-b4ee-4293-b362-1e0175ebe337 | os-compute08.maas |
|   cell1   | d3dfd353-b4ee-4293-b362-1e0175ebe337 | os-compute09.maas |
+-----------+--------------------------------------+-------------------+

$ sudo nova-manage cell_v2 discover_hosts --verbose
Modules with known eventlet monkey patching issues were imported prior to eventlet monkey patching: urllib3. This warning can usually be ignored if the caller is only importing and not executing nova code.
Deprecated: Option "logdir" from group "DEFAULT" is deprecated. Use option "log-dir" from group "DEFAULT".
Found 2 cell mappings.
Skipping cell0 since it does not contain hosts.
Getting computes from cell 'cell1': d3dfd353-b4ee-4293-b362-1e0175ebe337
Found 0 unmapped computes in cell: d3dfd353-b4ee-4293-b362-1e0175ebe337

我同样尝试重新启动 nova 控制器：

$ sudo systemctl restart nova-scheduler
$ sudo systemctl restart nova-conductor

重新启动 nova 控制器时，日志会显示以下内容：

2024-10-18 11:53:44.939 630048 INFO nova.scheduler.host_manager [None req-eb8c8117-136c-4a13-ac57-d32d4099388a - - - - - -] Received a sync request from an unknown host 'os-compute09.maas'. Re-created its InstanceList.
2024-10-18 11:53:44.939 630046 INFO nova.scheduler.host_manager [None req-eb8c8117-136c-4a13-ac57-d32d4099388a - - - - - -] Received a sync request from an unknown host 'os-compute09.maas'. Re-created its InstanceList.
2024-10-18 11:53:44.940 630045 INFO nova.scheduler.host_manager [None req-eb8c8117-136c-4a13-ac57-d32d4099388a - - - - - -] Received a sync request from an unknown host 'os-compute09.maas'. Re-created its InstanceList.
2024-10-18 11:53:44.968 630047 INFO nova.scheduler.host_manager [None req-eb8c8117-136c-4a13-ac57-d32d4099388a - - - - - -] Received a sync request from an unknown host 'os-compute09.maas'. Re-created its InstanceList.
2024-10-18 11:54:02.539 630048 INFO nova.scheduler.host_manager [None req-ad410200-f99f-4dc7-896d-637dd9620568 - - - - - -] Received a sync request from an unknown host 'os-compute04.maas'. Re-created its InstanceList.
2024-10-18 11:54:02.541 630047 INFO nova.scheduler.host_manager [None req-ad410200-f99f-4dc7-896d-637dd9620568 - - - - - -] Received a sync request from an unknown host 'os-compute04.maas'. Re-created its InstanceList.
2024-10-18 11:54:02.542 630046 INFO nova.scheduler.host_manager [None req-ad410200-f99f-4dc7-896d-637dd9620568 - - - - - -] Received a sync request from an unknown host 'os-compute04.maas'. Re-created its InstanceList.
2024-10-18 11:54:02.543 630045 INFO nova.scheduler.host_manager [None req-ad410200-f99f-4dc7-896d-637dd9620568 - - - - - -] Received a sync request from an unknown host 'os-compute04.maas'. Re-created its InstanceList.
2024-10-18 11:55:06.432 630048 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Host mapping not found for host os-compute03.maas. Not tracking instance info for this host.
2024-10-18 11:55:06.432 630048 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Received a sync request from an unknown host 'os-compute03.maas'. Re-created its InstanceList.
2024-10-18 11:55:06.435 630047 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Host mapping not found for host os-compute03.maas. Not tracking instance info for this host.
2024-10-18 11:55:06.435 630046 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Host mapping not found for host os-compute03.maas. Not tracking instance info for this host.
2024-10-18 11:55:06.436 630045 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Host mapping not found for host os-compute03.maas. Not tracking instance info for this host.
2024-10-18 11:55:06.436 630047 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Received a sync request from an unknown host 'os-compute03.maas'. Re-created its InstanceList.
2024-10-18 11:55:06.437 630045 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Received a sync request from an unknown host 'os-compute03.maas'. Re-created its InstanceList.
2024-10-18 11:55:06.436 630046 INFO nova.scheduler.host_manager [None req-53ac9845-afb5-48ec-b24f-344d2afcfc3f - - - - - -] Received a sync request from an unknown host 'os-compute03.maas'. Re-created its InstanceList.

特别的是：Host mapping not found for host os-compute03.maas. Not tracking instance info for this host.我猜这是应该在nova cell_v2中添加节点的时候吧？事实并非如此。

我猜测数据库中的以下记录与计算节点有关：

mysql> SELECT hypervisor_hostname, host_ip FROM nova.compute_nodes;
+---------------------+----------+
| hypervisor_hostname | host_ip  |
+---------------------+----------+
| os-compute08.maas   | 10.0.1.8 |
| os-compute04.maas   | 10.0.1.4 |
| os-compute09.maas   | 10.0.1.9 |
| os-compute03.maas   | 10.0.1.3 |
+---------------------+----------+
4 rows in set (0.00 sec)

os-compute03.maas确实没有在nova_api.host_mappings表中列出：

SELECT * FROM nova_api.host_mappings;
+---------------------+------------+----+---------+-------------------+
| created_at          | updated_at | id | cell_id | host              |
+---------------------+------------+----+---------+-------------------+
| 2024-07-02 21:23:10 | NULL       |  1 |       2 | os-compute08.maas |
| 2024-07-02 21:23:11 | NULL       |  2 |       2 | os-compute04.maas |
| 2024-07-02 21:23:11 | NULL       |  3 |       2 | os-compute09.maas |
+---------------------+------------+----+---------+-------------------+

我没有尝试手动将主机添加到此表中。我认为这应该会自动完成，但什么时候完成？我错过了什么？

我们如何进一步调试这种情况？

kolla-ansible我有一个使用version安装的 Openstack (yoga) 集群14.1.0。

我正在尝试设置 OpenIDConnect 以通过 Horizo​​n 界面登录，因此我遵循了此文档。

我遇到的问题是，当尝试通过我设置的新身份提供商进行连接时，我被发送到此 URL，该 URL 响应404：

http://<openstack_hostname>:5000/auth/OS-FEDERATION/identity_providers/<idp_id>/protocols/openid/websso?origin=http://<openstack_hostname>/auth/websso/

据我所知，/v3/路径的开头缺少一个，而应该是：

http://<openstack_hostname>:5000/v3/auth/OS-FEDERATION/identity_providers/<idp_id>/protocols/openid/websso?origin=http://<openstack_hostname>/auth/websso/

当我手动输入该 URL 时，它会成功将我发送到身份提供者以继续登录过程。

我不知道这是怎么回事。据我查阅文档得知，URL 应该带有 ，/v3/但我不知道在我的安装中这个错误的 URL 是从哪里来的。

我在Ubuntu 20上使用devstack安装了openstack，并使用节点导出器安装了prometheus和grafana，它在grafana上显示没有问题，但是如何监控openstack组件Nova....grafana中有一个Openstack Exporter，但它显示为空

提前致谢

我有一个与 ceph 集成的 openstack。我正在研究在不使用 cinder_backup 模块的情况下创建实例卷副本的最快方法。在 Ceph 中，可以访问存储在池中（如卷池）的 rbd 文件，我们可以导出它们，然后从中创建映像并创建另一个实例。但还有另一种名为“Offload rbd's copy_volume_to_image”的方法https://specs.openstack.org/openstack/cinder-specs/specs/liberty/optimze-rbd-copy-volume-to-image.html 我想知道如何使用这些复制的卷来创建 Openstack 中的映像池，因为执行此操作后，映像位于 rbd 池中，但在 OpenStack 中不可用，因为 OpenStack 尚未生成它并且没有 OpenStack ID。我想知道你是否可以帮助我了解使用这种方法创建后如何使用图像。先感谢您。

我有一个带有 Ceph 后端的 OpenStack-kolla 环境。我已经使用 NFS 配置了我的 cinder 后端。我可以使用 Cinder 从所有实例创建备份并将它们存储在 NFS 上。在这种情况下，我不想将 Cinder 后端更改为 Ceph，但我想知道是否有一种方法可以像文件一样访问 Ceph 上的所有实例卷，然后从 ceph 提取/下载这些文件。我到底需要的是，例如，我有一个带有一个附加卷的实例。我想从 ceph 中提取该卷并保留它，并且能够将该卷导出到另一个 Openstack。我知道有一些方法可以将一个实例迁移到另一个 Openstack，但我想访问 Ceph 中的卷。先感谢您。

在RHEL/CentOS安装openstack的官方文章中，最后提到还要安装openstack-selinux“自动管理OpenStack服务的安全策略”。相同的软件包是否适用于 Rocky Linux？相关的开源存储库仅openstack-selinux在 RHEL 7 之前更新其政策，目前尚不清楚是否有更新政策以适应 RHEL/CentOS 9（以及 Rocky Linux）。

Web 上的安装指南只说明应该禁用 SELinux 和防火墙，是否可以在 Rocky 上安装 openstack，同时保持防火墙启用并执行 SELinux 策略？

如果您设置CLIFF_FIT_WIDTH=1，openstack cli 将使表格输出适合屏幕宽度。

但是，如果您尝试通过管道传输到 less，这就会中断。

似乎可能的解决方法是：alias openstack='openstack --max-width "$(tput cols)"'但这似乎很老套。是否有我错过的 openstack cli 的标志或 env var，以便我可以在不破坏宽度的情况下将输出传输到 less？

我正在 OpenStack 集群中进行实时迁移测试。（三鹰）。我在 2 个计算主机上部署了 3 个虚拟机。当我启动集群时，nova-compute 状态为 UP。但是一段时间后，尽管状态为已启用，但状态已关闭，因此我的虚拟机中断了。

root@ctl:/var/log/nova# openstack compute service list
+----+------------------+-------------------------------------------------------+----------+---------+-------+----------------------------+
| Id | Binary           | Host                                                  | Zone     | Status  | State | Updated At                 |
+----+------------------+-------------------------------------------------------+----------+---------+-------+----------------------------+
|  1 | nova-cert        | ctl.livemigration.kkprojects-pg0.clemson.cloudlab.us  | internal | enabled | up    | 2023-02-18T21:17:06.000000 |
|  2 | nova-consoleauth | ctl.livemigration.kkprojects-pg0.clemson.cloudlab.us  | internal | enabled | up    | 2023-02-18T21:17:06.000000 |
|  3 | nova-scheduler   | ctl.livemigration.kkprojects-pg0.clemson.cloudlab.us  | internal | enabled | up    | 2023-02-18T21:17:09.000000 |
|  7 | nova-conductor   | ctl.livemigration.kkprojects-pg0.clemson.cloudlab.us  | internal | enabled | up    | 2023-02-18T21:17:08.000000 |
| 11 | nova-compute     | cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us | nova     | enabled | down  | 2023-02-18T20:14:16.000000 |
| 12 | nova-compute     | cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us | nova     | enabled | down  | 2023-02-18T20:14:21.000000 |
+----+------------------+-------------------------------------------------------+----------+---------+-------+----------------------------+

检查计算节点上的 Nova Computes 我发现它们已启用

root@cp-2:/etc/selinux# hostname
cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us
root@cp-2:/etc/selinux# service nova-compute status
● nova-compute.service - OpenStack Compute
   Loaded: loaded (/lib/systemd/system/nova-compute.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2023-02-18 14:20:22 EST; 1h 58min ago
 Main PID: 9926 (nova-compute)
   CGroup: /system.slice/nova-compute.service
           └─9926 /usr/bin/python /usr/bin/nova-compute --config-file=/etc/nova/nova.conf --config-file=/etc/nova/nova-compute.conf --log-file=/var/log/nova/nova-compute.log

Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19697]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19697]: pam_unix(sudo:session): session closed for user root
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19703]:     nova : TTY=unknown ; PWD=/var/lib/nova ; USER=root ; COMMAND=/usr/bin/nova-rootwrap /etc/nova/rootwrap.conf o
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19703]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us ovs-vsctl[19706]: ovs|00001|vsctl|INFO|Called as /usr/bin/ovs-vsctl --timeout=120 -- --if-exists del-port qvo8e68056c-a0 -- ad
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19703]: pam_unix(sudo:session): session closed for user root
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19707]:     nova : TTY=unknown ; PWD=/var/lib/nova ; USER=root ; COMMAND=/usr/bin/nova-rootwrap /etc/nova/rootwrap.conf i
Feb 18 14:59:07 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[19707]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 18 15:00:25 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[20242]:     nova : TTY=unknown ; PWD=/var/lib/nova ; USER=root ; COMMAND=/usr/bin/nova-rootwrap /etc/nova/rootwrap.conf t
Feb 18 15:00:25 cp-2.livemigration.kkprojects-pg0.clemson.cloudlab.us sudo[20242]: pam_unix(sudo:session): session opened for user root by (uid=0)

root@cp-1:/var/log/nova# hostname
cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us
root@cp-1:/var/log/nova# service  nova-compute status
● nova-compute.service - OpenStack Compute
   Loaded: loaded (/lib/systemd/system/nova-compute.service; enabled; vendor preset: enabled)
   Active: active (running) since Sat 2023-02-18 15:37:11 EST; 42min ago
  Process: 28530 ExecStartPre=/bin/chown nova:nova /var/lock/nova /var/log/nova /var/lib/nova (code=exited, status=0/SUCCESS)
  Process: 28527 ExecStartPre=/bin/mkdir -p /var/lock/nova /var/log/nova /var/lib/nova (code=exited, status=0/SUCCESS)
 Main PID: 28533 (nova-compute)
   CGroup: /system.slice/nova-compute.service
           └─28533 /usr/bin/python /usr/bin/nova-compute --config-file=/etc/nova/nova.conf --config-file=/etc/nova/nova-compute.conf --log-file=/var/log/nova/nova-compute.log

Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.281 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.283 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.283 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.285 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.287 28533 DEBUG nova.virt.libvirt.vif [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: s=<?>,shutdown_terminate=False,system_metadata=<?>,tags=<?>,task_state=None,terminated_at=None,updated_at
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.289 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.291 28533 DEBUG nova.compute.manager [req-df86d8a0-a7ff-480d-b157-39ae745850fd - - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.346 28533 WARNING nova.compute.monitors [req-df86d8a0-a7ff-480d-b157-39ae745850fd - -
Feb 18 15:37:15 cp-1.livemigration.kkprojects-pg0.clemson.cloudlab.us nova-compute[28533]: 2023-02-18 15:37:15.347 28533 INFO nova.compute.resource_tracker [req-df86d8a0-a7ff-480d-b157-39ae745850f
lines 1-19/19 (END)

在 depoloying openstack ansible 之后启动我的第一个虚拟机。

实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 的构建已中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 不可接受：图像没有关联数据

回溯（最近调用最后）：文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/compute/manager.py”，第 2489 行，在 _build_and_run_instance self.driver.spawn （上下文，实例，image_meta，文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/virt/libvirt/driver.py”，第 4306 行，在 spawn created_instance_dir，created_disks = self._create_image( 文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/virt/libvirt/driver.py”, line 4701, in _create_image created_disks = self._create_and_inject_local_root( File “/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/virt/libvirt/driver.py”，第 4829 行，在 _create_and_inject_local_root self._try_fetch_image_cache（后端，fetch_func，上下文，文件“ /openstack/venvs/nova-25.2.0/lib/python3。10/site-packages/nova/virt/libvirt/driver.py”，第 10621 行，在 _try_fetch_image_cache image.cache（fetch_func=fetch_func，文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site -packages/nova/virt/libvirt/imagebackend.py", line 274, in cache self.create_image(fetch_func_sync, base, size, File "/openstack/venvs/nova-25.2.0/lib/python3.10/site- packages/nova/virt/libvirt/imagebackend.py”，第 638 行，在 create_image prepare_template(target=base, *args, **kwargs) 文件“/openstack/venvs/nova-25.2.0/lib/python3.10/ site-packages/oslo_concurrency/lockutils.py”，第 391 行，在内部返回 f(*args, **kwargs) 文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova /virt/libvirt/imagebackend.py”，第 271 行，在 fetch_func_sync fetch_func(target=target, *args, **kwargs) 文件“/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/virt/libvirt/utils.py”，第 395 行，在 fetch_image images.fetch_to_raw(context, image_id, target, trusted_certs) 文件“/openstack/venvs/nova-25.2 .0/lib/python3.10/site-packages/nova/virt/images.py”，第 115 行，在 fetch_to_raw fetch(context, image_href, path_tmp, trusted_certs) 文件“/openstack/venvs/nova-25.2.0/ lib/python3.10/site-packages/nova/virt/images.py”，第 105 行，在 fetch IMAGE_API.download(context, image_href, dest_path=path, File “/openstack/venvs/nova-25.2.0/lib /python3.10/site-packages/nova/image/glance.py", line 1298, in download return session.download(context, image_id, data=data, File "/openstack/venvs/nova-25.2.0/lib /python3.10/site-packages/nova/image/glance.py”，第 384 行，在下载中引发异常。ImageUnacceptable(image_id=image_id, nova.exception。ImageUnacceptable: Image 272e3979-c387-4651-84e5-1adcdebfa955 is acceptable: Image has no associated data 在处理上述异常的过程中，又发生了一个异常：Traceback (most recent call last): File "/openstack/venvs/nova-25.2. 0/lib/python3.10/site-packages/nova/compute/manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib /python3.10/site-packages/nova/compute/manager.py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178 -aada6a302a4a 中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 不可接受：图像没有关联数据Image 272e3979-c387-4651-84e5-1adcdebfa955 is acceptable: Image has no associated data 在处理上述异常的过程中，又出现了异常： Traceback (most recent call last): File "/openstack/venvs/nova-25.2.0/ lib/python3.10/site-packages/nova/compute/manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3 .10/site-packages/nova/compute/manager.py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 不可接受：图像没有关联数据Image 272e3979-c387-4651-84e5-1adcdebfa955 is acceptable: Image has no associated data 在处理上述异常的过程中，又出现了异常： Traceback (most recent call last): File "/openstack/venvs/nova-25.2.0/ lib/python3.10/site-packages/nova/compute/manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3 .10/site-packages/nova/compute/manager.py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 不可接受：图像没有关联数据Image has no associated data 在处理上述异常的过程中，又出现了一个异常：Traceback (most recent call last): File "/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/compute /manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/compute/manager. py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 中止：图像 272e3979-c387-4651-84efa5-1不可接受：图像没有关联数据Image has no associated data 在处理上述异常的过程中，又出现了一个异常：Traceback (most recent call last): File "/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/compute /manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3.10/site-packages/nova/compute/manager. py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 中止：图像 272e3979-c387-4651-84efa5-1不可接受：图像没有关联数据10/site-packages/nova/compute/manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3.10/site -packages/nova/compute/manager.py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 中止：图像 272e3979 -c387-4651-84e5-1adcdebfa955 是不可接受的：图像没有关联数据10/site-packages/nova/compute/manager.py”，第 2312 行，在 _do_build_and_run_instance self._build_and_run_instance(context, instance, image, File “/openstack/venvs/nova-25.2.0/lib/python3.10/site -packages/nova/compute/manager.py”，第 2574 行，在 _build_and_run_instance 引发异常。BuildAbortException（instance_uuid=instance.uuid，nova.exception.BuildAbortException：构建实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 中止：图像 272e3979 -c387-4651-84e5-1adcdebfa955 是不可接受的：图像没有关联数据nova.exception.BuildAbortException：实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 的构建中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 是不可接受的：图像没有关联数据nova.exception.BuildAbortException：实例 7a91b5e8-23cc-4ec3-9178-aada6a302a4a 的构建中止：图像 272e3979-c387-4651-84e5-1adcdebfa955 是不可接受的：图像没有关联数据

图片：cirros-0.5.1-x86_64-disk.img
风味：m1.small（2Gb 内存，1 个 cpu，30gb 磁盘）