openstack创建实例报Build of instance d401db9e-xxxx-97c5d7685592 aborted: Unknown auth type: None

OpenStack实例创建失败：Unknown auth type与资源提供者冲突

最新推荐文章于 2023-03-21 20:10:26 发布

原创

最新推荐文章于 2023-03-21 20:10:26 发布 · 4k 阅读

2 ·

CC 4.0 BY-SA版权

在尝试通过OpenStack Dashboard创建实例时遇到'Build of instance... aborted: Unknown auth type: None'错误。经过一系列排查，包括检查keystone认证、手动创建实例、查看nova-conductor和nova-compute日志，发现资源提供者创建失败和409冲突错误。尝试删除并重新创建nova用户、服务和endpoint，问题依旧。最终通过删除数据库并重新初始化keystone、glance、nova、neutron、placement和cinder服务的数据库，同步数据并创建实例类型，成功解决问题。

这是在Dashborad界面得到以上报错

排查半天没有任何结果，发现keystone还是报认证错误。controller其他日志正常。

通过shell手动创建实例

[root@controller ~]#openstack server create --flavor m1.tiny --image cirros --nic net-id=3e4bc802-7e7f-49be-a9ae-f6216013b2c6 --availability-zone nova:compute-3:compute-3 test-node3

发行又出现了 No valid host was found. There are not enough hosts available.错误。

[root@controller nova]# cat nova-conductor.log ##日志报错信息还是指向NoValidHost: No valid host was found. There are not enough hosts available.

[root@compute-3 nova]# cat nova-compute.log ##一直在循环报错 Error updating resources for node compute-3: ResourceProviderCreationFailed: Failed to create resource provider compute-3

[root@compute-3 nova]# cat nova-compute.log

2020-12-17 14:49:06.272 2529 ERROR nova.scheduler.client.report [req-98d36e66-25a2-40de-8e25-7d1f489b0588 - - - - -] [req-5353573f-da11-48ff-8472-1e9a471269cd] Failed to create resource provider record in placement API for UUID b1c484e8-58cb-41d5-84d3-1e1f4ffab341. Got 409: {"errors": [{"status": 409, "request_id": "req-5353573f-da11-48ff-8472-1e9a471269cd", "detail": "There was a conflict when trying to complete your request.\n\n Conflicting resource provider name: compute-3.rocky2.yfb0801800.islab.net.cn already exists. ", "title": "Conflict"}]}.

2020-12-17 14:49:06.272 2529 ERROR nova.compute.manager [req-98d36e66-25a2-40de-8e25-7d1f489b0588 - - - - -] Error updating resources for node compute-3: ResourceProviderCreationFailed: Failed to create resource provider compute-3

2020-12-17 14:49:06.272 2529 ERROR nova.compute.manager Traceback (most recent call last):

因为已经做过多次的su -s /bin/sh -c "nova-manage cell_v2 discover_hosts --verbose" nova。判断数据库出问题的可能性不大。怀疑keystone的nova用户权限有问题

检查openstack状态和nova计算节点，表面上看状态一切正常

最低0.47元/天解锁文章