On Thu, Oct 5, 2017 at 3:15 AM, Sam Hague <shague@redhat.com> wrote:
On Oct 4, 2017 8:56 PM, "Michael Vorburger" <vorburger@redhat.com> wrote:
On Wed, Oct 4, 2017 at 11:42 PM, Sam Hague <shague@redhat.com> wrote:
Michael,
can you fill me in on what the below is? This popped out in a csit gate job, but I have never seen this before. Verify jobs all pass. What is weird is this only seems to come out in these gate jobs but that doesn't make sense at all.
it's an INFO not an ERROR.. which I need to change to be less shocking - on my TODO list, just didn't get to it yet.
Ok, main concern was to make sure it was not an error. Ans weird it only comes out sometimes.
You probably only see it sometimes because if it starts up fast enough, there will be or less of it.
So guess you are saying there isn't a problem right?
Yeah, it's not a problem at all - FYI this is just the SFT-like INFO log of my ready service work at start-up..
This is actually the same as the point also raised in thread "[ODL | NIC | Genius dependence - 'due to Blueprint' log]" on genius-dev, see https://lists.opendaylight.org/pipermail/genius-dev/2017-September/thread.html#1896 ...
The current logging from (my) infrautils.ready system at boot, exactly like SFT at build, while completely harmless 
as just INFO, seems to confuse more people looking at logs than I would have thought...
So let me change that, better idea: Let's log INFO one liners (like
{Installed=0, Failure=0, Waiting=0, [939/1928], Stopping=0, Unknown=0, GracePeriod=23, Starting=0, Resolved=15}), but keep those multi-line NOK/Missing depenencies details which it seems are confusing people at level DEBUG only (unless it stay like that for a "long time" - and then ERROR log that, only once).
Implemented and ready for review, needs odlparent change & new release:
With the odlparent bump now having happened, I can merge c/66013 now. (In case we do globally revert after all, we'll just have to revert that again.)