nova compute冲突

Conflicting resource provider name: compute01 already exists.

v版本openstack，目前怀疑nova-scheduler 配置错误，调了filter_scheduler,导致注册了一批错误的nova-compute，

其中一批通过删除 nova_cell0 中的重复的services 数据解决了，
但是还是有两台报

Conflicting resource provider name: compute01 already exists.
Conflicting resource provider name: compute02 already exists.

然后发现 nova_api compute_nodes 中有重复的compute01 compute02 数据，所以删除

然后 把placement中 compute01 compute02 修改为 compute_nodes 中 compute01 compute02 的uuid
resource_providers 中的
resource_provider_traits

不要直接删除，更新uuid即可，否则还要还原数据

MariaDB [placement]> SET FOREIGN_KEY_CHECKS = 0;
Query OK, 0 rows affected (0.000 sec)

MariaDB [placement]> update resource_providers set id=9 where name='compute02';
Query OK, 1 row affected (0.002 sec)
Rows matched: 1 Changed: 1 Warnings: 0

MariaDB [placement]> update resource_providers set id=6 where name='compute01';
Query OK, 1 row affected (0.002 sec)
Rows matched: 1 Changed: 1 Warnings: 0

MariaDB [placement]> update resource_providers set root_provider_id=6 where name='compute01';
Query OK, 1 row affected (0.002 sec)
Rows matched: 1 Changed: 1 Warnings: 0

MariaDB [placement]> update resource_providers set root_provider_id=9 where name='compute02';
Query OK, 1 row affected (0.002 sec)
Rows matched: 1 Changed: 1 Warnings: 0

MariaDB [placement]> SET FOREIGN_KEY_CHECKS = 1;
Query OK, 0 rows affected (0.000 sec)