And that is the whole fun point of it all: AICCU (or anything else) cannot fix network problems time issues or wrongly entered passwords automagically either....
Hence why it logs a message to what the problem is and EXITS. Note: it does not *crash* as what everybody seems to call a proper exit(code) call.
Restarting AICCU thus does not resolve anything unless the administrator of the host intervenes by fixing the relevant problem.
As for "Fedora fixing it", checking: http://pkgs.fedoraproject.org/... there is no "fix" there, they just added the requested "wait for ntp sync" flag to systemd which only solves one small part of the problem (no valid time yet, at which point one cannot do crypto, thus why are you connecting to online services at all?).
Without functional network connectivity it still won't start though, and that makes sense as there is nothing to connect to and thus it cannot do anything, hence it properly logs a message (that clearly nobody reads, because why would one read log messages) and then exits.
Note that systemd/Redhat folks are not the only ones who do not seem to understand the real problem here and think they can magically "fix" things while the host itself is not the problem (eg no network connectivity, broken connectivity, broken time setting, broken timezone setting, wrong password etc etc etc).