Ask Your Question
1

No host-to-cell mapping found for selected host controller. Setup is incomplete.

asked 2017-08-31 00:25:16 -0500

liaodalin19903 gravatar image

updated 2017-08-31 01:06:27 -0500

I create the VM failed, in the /var/log/nova/nova-conductor.log I found the bellow error:

 2017-08-31 12:27:26.368 26328 ERROR nova.conductor.manager [req-5f682dbb-d7a7-471e-ab83-d258257767d1 - - - - -] No host-to-cell mapping found for selected host controller. Setup is incomplete.
2017-08-31 12:27:26.579 26328 WARNING nova.scheduler.utils [req-5f682dbb-d7a7-471e-ab83-d258257767d1 - - - - -] compute_task_build_instances 失败(failture):主机(host) 'controller'没有映射
到任何单元(has no mapping to any unit)
2017-08-31 12:27:26.580 26328 WARNING nova.scheduler.utils [req-5f682dbb-d7a7-471e-ab83-d258257767d1 - - - - -] [instance: ec4477d0-e167-4d06-97d5-bc40d644335d] 设置实例到 ERROR 状态。(set instance to ERROR status)

EDIT-1

I set the controller and computer in one node.


EDIT-2

I tried the :nova-manage cell_v2 discover_hosts but do not work for me.

edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2018-02-22 05:39:34 -0500

if you have changed your HOSTNAME the do these steps: 1- Revert the hostname

[root@localhost ~]# source /root/keystonerc_admin [root@localhost ~(keystone_admin)]# nova service-list +--------------------------------------+------------------+-----------------------+----------+---------+-------+----------------------------+-----------------+-------------+ | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason | Forced down | +--------------------------------------+------------------+-----------------------+----------+---------+-------+----------------------------+-----------------+-------------+ | 50b9bef1-2c9d-4d11-8a7e-30f31c1f7e11 | nova-conductor | localhost.localdomain | internal | enabled | down | 2018-02-22T09:43:11.000000 | - | False | | 5a750f47-98fc-4386-8eae-9e0f5135eee2 | nova-scheduler | localhost.localdomain | internal | enabled | down | 2018-02-22T09:43:26.000000 | - | False | | 488400d1-3305-484b-9619-5ee475f79bf6 | nova-consoleauth | localhost.localdomain | internal | enabled | down | 2018-02-22T09:43:52.000000 | - | False | | 7f2e70bb-0e41-44b1-a8cf-2446c4f8080a | nova-compute | localhost.localdomain | nova | enabled | down | 2018-02-22T10:25:13.000000 | - | False | | 4b8c5344-a1e2-43ee-94fa-b4a1c6f6dd16 | nova-conductor | pike | internal | enabled | down | 2018-02-22T10:45:35.000000 | - | False | | d0039534-99af-4e0b-bd29-10c55c9128b1 | nova-scheduler | pike | internal | enabled | down | 2018-02-22T10:45:36.000000 | - | False | | 8798ba9e-c424-47fd-8b35-b109185aa0f5 | nova-consoleauth | pike | internal | enabled | down | 2018-02-22T10:45:35.000000 | - | False | | 335ba796-59f0-442d-870f-e71ae25c0e38 | nova-compute | pike | nova | enabled | down | 2018-02-22T10:45:38.000000 | - | False |

2- Delete the Services with are down and belong to the hostname you tried to changed with like for me "Pike"

[root@localhost ~(keystone_admin)]# nova service-delete 4b8c5344-a1e2-43ee-94fa-b4a1c6f6dd16 [root@localhost ~(keystone_admin)]# nova service-delete d0039534-99af-4e0b-bd29-10c55c9128b1 [root@localhost ~(keystone_admin)]# nova service-delete 8798ba9e-c424-47fd-8b35-b109185aa0f5 [root@localhost ~(keystone_admin)]# nova service-delete 335ba796-59f0-442d-870f-e71ae25c0e38

3- try creating new instance

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2017-08-31 00:25:16 -0500

Seen: 2,314 times

Last updated: Feb 22 '18