Comment 11 for bug 1883038

Reviewed: https://review.opendev.org/c/openstack/oslo.messaging/+/744262
Committed: https://opendev.org/openstack/oslo.messaging/commit/54ced5361b49fb9b0cf53ff2e6f5825ba7ae513a
Submitter: "Zuul (22348)"
Branch: stable/train

commit 54ced5361b49fb9b0cf53ff2e6f5825ba7ae513a
Author: shenjiatong <email address hidden>
Date: Tue Jun 30 08:56:26 2020 +0800

    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.

    [1] https://stackoverflow.com/q/33743880/

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