Catch ConnectionForced Exception

Occasionally I saw large number of connectionforced exceptions.
such exceptions cannot be healed automatically and requires a reboot.
catch it and ensure connection established.

Changes:
  oslo_messaging/_drivers/impl_rabbit.py

NOTE(stephenfin): We need to add the 'absolute_import' future to disable
the legacy import flow. Without this, the import of 'amqp.exceptions' in
'oslo_messaging._drivers.impl_rabbit' attempts to import 'exceptions'
from the sibling module, 'oslo_messaging._drivers.amqp', instead of the
top-level 'amqp' module. Thank God for Python 3.x, eh? More information
is available at [1], for those curious enough.

NOTE(hberaud): conflicts within the cherry-pick on stable/stein due to
removed log translation and i18n on stable/train [2]. I decided to ignore this
patch [2] for stable/stein first to prepare cherry-picking on previous stable
branches (rocky, queens) and secondly because I don't think we want it
on older branches.

[1] https://stackoverflow.com/q/33743880/
[2]
https://opendev.org/openstack/oslo.messaging/commit/4f385720d7d43aadfaff7c6f41b0534312b23ba8

Change-Id: I5c468d10230f05438df780e045f1e92662edf070
Closes-Bug: #1883038
(cherry picked from commit 26e8bb4cc9097fddf3c2e34599b131e3f5d73867)
(cherry picked from commit 360deb89a7e95d332267564b486219e389a793f7)
(cherry picked from commit 54ced5361b49fb9b0cf53ff2e6f5825ba7ae513a)

0 files changed, 0 insertions, 0 deletions