And that is the whole fun point of it all: AICCU (or anything else) cannot fix network problems
It's not supposed to fix them, it's supposed to retry until they've been fixed externally. And no, you don't expect a user to "read log messages" and restart the thing manually every time the network is unavailable. A network outage is fixed where it happens, it's not supposed to break thousands of daemons downstream permanently until somebody has read their logfiles and manually restarted them like an idiot. There may not even be a user, if you think of unattended server boxes or, say, home routers running in your mom's basement. Your mom won't read log files. And she certainly doesn't want to power-cycle her internet box every time the network comes up again (or wasn't up when she switched the box on). This thing wants to be a Unix-style daemon that's supposed to support robust automation, not requiring a c00l h4xx0r type holding its hand and reading log files and typing fancy restart commands all the time to do stuff that's blatantly obvious anyway.
You should really step back for a minute and think this over and change your perspective. You were thrown into that Redhat bugzilla because you were angry because someone had made a wrong fix that DDoSed your service, without contacting you first, and apparently that anger has clouded your judgment, or so it seems.