Bug #25635892 'STARTING CONNECT THREAD' SHOULD BE LOGGED AS AN 'INFO', NOT 'WARNING'

As subject says: The message 'starting connect thread' should be an
'information' instead of a 'warning' as this a completely
harmless situation.

Author: Ole John Aske

mysql-test/suite/ndb/r/ndb_bushy_joins.result

@@ -30,7 +30,6 @@ test.parent	analyze	status	OK
 test.eq_child	analyze	status	OK
 test.ref_child	analyze	status	OK
 set ndb_join_pushdown = on;
-call mtr.add_suppression("starting connect thread");
 ===============================
 Run single instance of 'query1' 
 ===============================

mysql-test/suite/ndb/t/ndb_bushy_joins.test

@@ -163,8 +163,6 @@ let $query4 =
 connection j1;
 set ndb_join_pushdown = on;
 
-call mtr.add_suppression("starting connect thread");
-
 -- echo ===============================
 -- echo Run single instance of 'query1' 
 -- echo ===============================

sql/ha_ndbcluster_connection.cc

@@ -1,5 +1,5 @@
 /*
-   Copyright (c) 2000, 2013, Oracle and/or its affiliates. All rights reserved.
+   Copyright (c) 2000, 2017, Oracle and/or its affiliates. All rights reserved.
 
    This program is free software; you can redistribute it and/or modify
    it under the terms of the GNU General Public License as published by
@@ -149,7 +149,7 @@ ndbcluster_connect(int (*connect_callback)(void),
         g_pool[i]->connect(0,0,0);
         if (g_pool[i]->node_id() == 0)
         {
-          sql_print_warning("NDB[%u]: starting connect thread", i);
+          sql_print_information("NDB[%u]: starting connect thread", i);
           g_pool[i]->start_connect_thread();
           continue;
         }