Service start is not reliable with any network initialization issues

[Jorge Niedbalski]

[Environment]

Juju-Core 1.25.3
Trusty 14.04.3

[Description]

The jujud service (machine and unit) is started via upstart on runlevel 2345, but this condition should
be extended to wait for a couple of additional events (static-network-up and net-device-up IFACE != lo),
so on that manner the service will be started only if all the network devices are up and also all the interfaces flagged as auto are up.

On that note, there are not so uncommon events such as a delayed DHCP server taking a few seconds to configure a network interface, that will eventually affect some logic as address-selection and charms that depends on specific networks to be available.
(ceph, as an example).

So I think that the start stanza should look like:

start on runlevel [2345] and (static-network-up and net-device-up IFACE!=lo)

Instead of just start on runlevel [2345]

[Cheryl Jennings (cherylj)]

Jorge - if you have any logs that show symptoms or errors, can you upload them?

[Jorge Niedbalski (niedbalski)]

I included a pre-start script for validating that all the auto interfaces are up && dhcp configured.

Reference: http://paste.ubuntu.com/15577670/

[Anastasia (anastasia-macmood)]

@Jorge,
Could you please replicate with most recent beta for 2.0 and attach logs?