Just to clarify, this isn't specific to the openstack provider. Here is a bare metal deployment using the maas provider, where 2 metal units failed to come up (separate issue from this bug), and juju-deployer hasn't exited after nearly 1 day. The timeout threshold is not kicking in, and the "deploy is ready" logic is apparently still churning.
Just to clarify, this isn't specific to the openstack provider. Here is a bare metal deployment using the maas provider, where 2 metal units failed to come up (separate issue from this bug), and juju-deployer hasn't exited after nearly 1 day. The timeout threshold is not kicking in, and the "deploy is ready" logic is apparently still churning.
http:// paste.ubuntu. com/13101588/