Bug 1447355
| Summary: | OSP10 -> OSP11 upgrade: nova instance live migration gets stuck with MIGRATING status before running compute node upgrade | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | John Eckersberg <jeckersb> |
| Component: | rabbitmq-server | Assignee: | John Eckersberg <jeckersb> |
| Status: | CLOSED ERRATA | QA Contact: | Udi Shkalim <ushkalim> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 11.0 (Ocata) | CC: | apevec, dbecker, dmacpher, fdinitto, jcoufal, jeckersb, jschluet, lhh, mabaakou, mandreou, markmc, mburns, mcornea, michele, morazi, panbalag, plemenko, rhel-osp-director-maint, rscarazz, sasha, sathlang, sclewis, slinaber, srevivo, ushkalim, vstinner |
| Target Milestone: | async | Keywords: | Triaged, ZStream |
| Target Release: | 11.0 (Ocata) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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.
|
Story Points: | --- |
| Clone Of: | 1441635 | Environment: | |
| Last Closed: | 2017-06-15 16:56:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1436784, 1441635 | ||
| Bug Blocks: | |||
|
Comment 1
John Eckersberg
2017-05-02 13:50:11 UTC
This fix was tested and verified in the original bug. Verified sanity only - rabbitmq-server-3.6.5-5.el7ost.noarch 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 |