msg/async: reduce verbosity of connection timeout failures

Long running clients connected to thrashing OSDs could result in a
"see no progress in more than <timeout>" message printed to stderr.
This is not an error but can result in test failures when console
output is compared against expected output.

Fixes: http://tracker.ceph.com/issues/39448
Signed-off-by: Jason Dillaman <dillaman@redhat.com>

diff --git a/src/msg/async/AsyncConnection.cc b/src/msg/async/AsyncConnection.cc
index 6100ff2995e0bbfa13a552544cccacdbcc112c35..74ad6cd5d0fd28146bb475c08739396220f6004d 100644 (file)
--- a/src/msg/async/AsyncConnection.cc
+++ b/src/msg/async/AsyncConnection.cc
@@ -757,7 +757,7 @@ void AsyncConnection::tick(uint64_t id)
     if (connect_timeout_us <=
         (uint64_t)std::chrono::duration_cast<std::chrono::microseconds>
           (now - last_connect_started).count()) {
-      ldout(async_msgr->cct, 0) << __func__ << " see no progress in more than "
+      ldout(async_msgr->cct, 1) << __func__ << " see no progress in more than "
                                 << connect_timeout_us
                                 << " us during connecting, fault."
                                 << dendl;