Comment 9 for bug 1512908

The compute host records are created by the nova-conductor service as the nova-compute daemons startup - there is code in the charms to ensure that compute daemons are restarted after the nova database etc.. has been setup and the conductors are in a state where they should be ready to process rpc calls from compute services.

A few more bits of information may help us ID where the problem is; specifically

1) logs from /var/log/nova from cloud-controller and nova-compute instances
2) the output of nova service-list - this will show all registered services, including ones that are down. (host-list is up only)