Comment 9 for bug 1577556

"The unit is reachable and the console log ..." do you mean the machine? (Generally unit has to do with a particular installation of an application.)

It would be interesting to have the context of cloud-init-output.log and machine-X.log as well as the 'machine-0.log' from the controller.

I don't think we can fire any hooks until we have addresses, because the machine agent is the thing that starts the unit agent, and it would have reported its addresses as the first action.

Its possible it is something like the "juju agent fails to get installed", or "the juju agent fails to contact the controller", which leaves us in a state where we know the machine we want to put the Unit on, but as far as we can tell that machine is not ready for us. (As signaled by the machine agent calling back to the controller.)

As soon as you do a "deploy" or an "add-unit", Juju has a record of the Unit you want to be adding, so just having that unit in "pending" state or waiting for "allocation" doesn't mean we've actually gotten to the point where we can do anything with that unit.

Other sources of context are things like "juju status --format=yaml" which includes a lot of details that don't fit well in tabular view.