After bootstrapping controller for Openstack cloud successfully (juju status returned ok), we then tried to ‘add-machine’, but the status of machine remained pending and no new instances created in Openstack.
We checked ‘machine-0.log’ in the controller instance and found some errors there:
2020-09-20 05:05:12 ERROR juju.worker.dependency engine.go:671 “broker-tracker” manifold worker returned unexpected error: no container types determined
2020-09-20 05:05:22 ERROR juju.core.raftlease store.go:265 timeout waiting for Command(ver: 1, op: claim, ns: singular-controller, model: dfa45c, lease: dfa45c42-cd34-47f2-86cd-bcd130d34ac4, holder: machine-0) to be processed
The timeout errors occurred repeatedly in the log.
Status of controller was also weird. When we called juju from client, the command usually got stuck, then we checked the port in controller and no port was bound at that time, but after a while, a binding of 17070 on specific ip appeared and the client command completed.
We tried the process(bootstrap, add-machine, waiting without progress and destroy controller) many times, and the results were almost always the same. But oddly enough, in one of those attempts, a corresponding machine was created.
Any suggestions?