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>
(cherry picked from commit 6b4f9729fd7cec14352b74cb3674a893159a1aa5)

diff --git a/src/msg/async/AsyncConnection.cc b/src/msg/async/AsyncConnection.cc
index 3199a345393ace1426f71df2716a41c7602084a3..eb0db916b46e683389d3534fa43fb3c40417cbd4 100644 (file)
--- a/src/msg/async/AsyncConnection.cc
+++ b/src/msg/async/AsyncConnection.cc
@@ -2608,7 +2608,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;