Bug 1447355 - OSP10 -> OSP11 upgrade: nova instance live migration gets stuck with MIGRATING status before running compute node upgrade
Summary: OSP10 -> OSP11 upgrade: nova instance live migration gets stuck with MIGRATIN...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: rabbitmq-server
Version: 11.0 (Ocata)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: async
: 11.0 (Ocata)
Assignee: John Eckersberg
QA Contact: Udi Shkalim
URL:
Whiteboard:
Depends On: 1436784 1441635
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-02 13:43 UTC by John Eckersberg
Modified: 2017-06-15 16:56 UTC (History)
26 users (show)

Fixed In Version: rabbitmq-server-3.6.5-5.el7ost
Doc Type: Bug Fix
Doc Text:
Networking issues related to changing IPv6 VIP source ports caused the RabbitMQ server to lose connectivity, which hindered live migration from running correctly. This caused problems when attempting to upgrade Compute nodes during an OpenStack Platform 10 to 11 upgrade. This update includes multiple fixes to correct the VIPs creation and change the RabbitMQ policy (ha-mode: all). RabbitMQ now runs correctly and provides successful live migration.
Clone Of: 1441635
Environment:
Last Closed: 2017-06-15 16:56:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github rabbitmq rabbitmq-server issues 1035 0 None None None 2017-05-02 13:43:20 UTC
Github rabbitmq rabbitmq-server issues 530 0 None None None 2017-05-02 13:43:20 UTC
Github rabbitmq rabbitmq-server issues 544 0 None None None 2017-05-02 13:43:20 UTC
Github rabbitmq rabbitmq-server issues 914 0 None None None 2017-05-02 13:47:08 UTC
Github rabbitmq rabbitmq-server issues 953 0 None None None 2017-05-02 13:47:53 UTC
Launchpad 1686357 0 None None None 2017-05-02 13:43:20 UTC
OpenStack gerrit 460202 0 None None None 2017-05-02 13:43:20 UTC
OpenStack gerrit 460204 0 None None None 2017-05-02 13:43:20 UTC
Red Hat Bugzilla 1441685 0 medium CLOSED RabbitMQ cannot reset the node after failure 2022-08-16 13:15:44 UTC
Red Hat Product Errata RHBA-2017:1473 0 normal SHIPPED_LIVE Red Hat OpenStack Platform 11.0 Bug Fix and Enhancement Advisory 2017-06-15 20:55:37 UTC

Comment 1 John Eckersberg 2017-05-02 13:50:11 UTC 
rabbitmq-server-3.6.5-5.el7ost contains fixes for https://github.com/rabbitmq/rabbitmq-server/issues/914 and https://github.com/rabbitmq/rabbitmq-server/issues/953 which causes rabbitmq cluster to effectively deadlock during partition as seen in the original bug.
Comment 7 Udi Shkalim 2017-06-05 14:27:21 UTC 
This fix was tested and verified in the original bug. Verified sanity only - rabbitmq-server-3.6.5-5.el7ost.noarch
Comment 9 errata-xmlrpc 2017-06-15 16:56:50 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1473
Note You need to log in before you can comment on or make changes to this bug.