«

Failed to create resource provider

指尖二进制 • 1 年前 • 788 次点击 • OPENSTACK


compute01日志

2023-06-02 22:29:47.893 18873 ERROR nova.compute.resource_tracker [req-78f82d34-dd2c-4a27-b1b7-3e9ff0808324 - - - - -] Skipping removal of allocations for deleted instances: Failed to retrieve allocations for resource provider 4c78068e-a236-472d-8071-817ffbbd04f3: {"errors": [{"status": 404, "request_id": "req-017dd408-ac99-4dd5-9faa-10ad519e94eb", "detail": "The resource could not be found.\n\n Resource provider '4c78068e-a236-472d-8071-817ffbbd04f3' not found: No resource provider with uuid 4c78068e-a236-472d-8071-817ffbbd04f3 found  ", "title": "Not Found"}]}: ResourceProviderAllocationRetrievalFailed: Failed to retrieve allocations for resource provider 4c78068e-a236-472d-8071-817ffbbd04f3: {"errors": [{"status": 404, "request_id": "req-017dd408-ac99-4dd5-9faa-10ad519e94eb", "detail": "The resource could not be found.\n\n Resource provider '4c78068e-a236-472d-8071-817ffbbd04f3' not found: No resource provider with uuid 4c78068e-a236-472d-8071-817ffbbd04f3 found  ", "title": "Not Found"}]}
2023-06-02 22:29:47.921 18873 ERROR nova.scheduler.client.report [req-78f82d34-dd2c-4a27-b1b7-3e9ff0808324 - - - - -] [req-5e623ae7-ab66-4bda-a233-a3da43154e80] Failed to create resource provider record in placement API for UUID 4c78068e-a236-472d-8071-817ffbbd04f3. Got 409: {"errors": [{"status": 409, "request_id": "req-5e623ae7-ab66-4bda-a233-a3da43154e80", "detail": "There was a conflict when trying to complete your request.\n\n Conflicting resource provider name: compute01 already exists.  ", "title": "Conflict"}]}.

compute02日志

2023-06-02 22:28:59.205 18945 ERROR nova.compute.resource_tracker [req-47e124ad-1828-45cd-8d39-ce01e2683d04 - - - - -] Skipping removal of allocations for deleted instances: Failed to retrieve allocations for resource provider ebefd159-5ce6-4416-b5e4-55d2a8646d91: {"errors": [{"status": 404, "request_id": "req-00237113-ce00-4db9-ba77-d6f42dc75d4d", "detail": "The resource could not be found.\n\n Resource provider 'ebefd159-5ce6-4416-b5e4-55d2a8646d91' not found: No resource provider with uuid ebefd159-5ce6-4416-b5e4-55d2a8646d91 found  ", "title": "Not Found"}]}: ResourceProviderAllocationRetrievalFailed: Failed to retrieve allocations for resource provider ebefd159-5ce6-4416-b5e4-55d2a8646d91: {"errors": [{"status": 404, "request_id": "req-00237113-ce00-4db9-ba77-d6f42dc75d4d", "detail": "The resource could not be found.\n\n Resource provider 'ebefd159-5ce6-4416-b5e4-55d2a8646d91' not found: No resource provider with uuid ebefd159-5ce6-4416-b5e4-55d2a8646d91 found  ", "title": "Not Found"}]}
2023-06-02 22:28:59.235 18945 ERROR nova.scheduler.client.report [req-47e124ad-1828-45cd-8d39-ce01e2683d04 - - - - -] [req-bfc1322e-7420-477c-a99b-ec198a89545d] Failed to create resource provider record in placement API for UUID ebefd159-5ce6-4416-b5e4-55d2a8646d91. Got 409: {"errors": [{"status": 409, "request_id": "req-bfc1322e-7420-477c-a99b-ec198a89545d", "detail": "There was a conflict when trying to complete your request.\n\n Conflicting resource provider name: compute02 already exists.  ", "title": "Conflict"}]}.

计算节点上openstack-nova-compute服务报错:

Failed to create resource provider computer02.

且这个计算节点无法被控制节点识别

解决办法:
检查控制节点数据库:
如下两个表中同一个计算节点的uuid应该是相同的,如果不同,需要以nova库compute_nodes表改成相同的(主要还是看报错提示的那是那个uuid);
我这个报错提示的是以nova库的compute_nodes表数据。所以placement库resource_providers表需要对照nova的compute_nodes修改。

MariaDB [(none)]> select uuid,name from placement.resource_providers;
+--------------------------------------+-----------+
| uuid                                 | name      |
+--------------------------------------+-----------+
| c3a9aec8-9508-4edc-a1e5-cfc59e8ee935 | compute02 |
| 148e67ca-33c7-4c6d-b631-3e280ce10a81 | compute01 |
+--------------------------------------+-----------+
2 rows in set (0.000 sec)

MariaDB [(none)]> select uuid,host from nova.compute_nodes;
+--------------------------------------+-----------+
| uuid                                 | host      |
+--------------------------------------+-----------+
| 4c78068e-a236-472d-8071-817ffbbd04f3 | compute01 |
| ebefd159-5ce6-4416-b5e4-55d2a8646d91 | compute02 |
+--------------------------------------+-----------+
2 rows in set (0.000 sec)

MariaDB [(none)]> UPDATE placement.resource_providers set uuid='4c78068e-a236-472d-8071-817ffbbd04f3'  where name='compute01';
MariaDB [(none)]> UPDATE placement.resource_providers set uuid='ebefd159-5ce6-4416-b5e4-55d2a8646d91'  where name='compute02';

MariaDB [(none)]> select uuid,name from placement.resource_providers;
+--------------------------------------+-----------+
| uuid                                 | name      |
+--------------------------------------+-----------+
| ebefd159-5ce6-4416-b5e4-55d2a8646d91 | compute02 |
| 4c78068e-a236-472d-8071-817ffbbd04f3 | compute01 |
+--------------------------------------+-----------+
2 rows in set (0.000 sec)

MariaDB [(none)]> select uuid,host from nova.compute_nodes;
+--------------------------------------+-----------+
| uuid                                 | host      |
+--------------------------------------+-----------+
| 4c78068e-a236-472d-8071-817ffbbd04f3 | compute01 |
| ebefd159-5ce6-4416-b5e4-55d2a8646d91 | compute02 |
+--------------------------------------+-----------+
2 rows in set (0.000 sec)
还没收到回复