Bug 1292527
Summary: | Backport: Support migration of non-HA router to HA and reverse | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Anderson Kaiser <akaiser> | |
Component: | openstack-neutron | Assignee: | John Schwarz <jschwarz> | |
Status: | CLOSED ERRATA | QA Contact: | Toni Freger <tfreger> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.0 (Kilo) | CC: | adahms, akaiser, amuller, chrisw, dcadzow, jschwarz, lpeer, nyechiel, srevivo, tfreger | |
Target Milestone: | --- | Keywords: | FeatureBackport, ZStream | |
Target Release: | 7.0 (Kilo) | |||
Hardware: | All | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-neutron-2015.1.2-10.el7ost | Doc Type: | Enhancement | |
Doc Text: |
With this update, legacy routers can now be migrated to an HA router, and vice versa. This allows users to migrate legacy routers to HA routers. To do so, users must unschedule the router from the existing agents, change the 'ha' attribute to 'True', then re-schedule it. Migration from an HA router to a non-HA router is also possible.
Users can use the following commands to migrate a router to and from HA:
neutron router-update --admin-state-up=False <ROUTER>
neutron router-update --ha=True/False <ROUTER>
neutron router-update --admin-state-up=True <ROUTER>
|
Story Points: | --- | |
Clone Of: | ||||
: | 1295690 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-22 19:16:48 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: | ||||
Bug Blocks: | 1295690 |
Description
Anderson Kaiser
2015-12-17 17:08:40 UTC
*** Bug 1292526 has been marked as a duplicate of this bug. *** I'm assuming you expect this backport to OSP 7, seeing as HA routers didn't exist in OSP 5? This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions The bug was flipped back to POST by accident in March. The bug should be in modified - The fix exists in the package in the 'Fixed in version' field and the doc text is set to '?'. Tested on openstack-neutron-2015.1.2-15.el7ost.noarch openstack-neutron-openvswitch-2015.1.2-15.el7ost.noarch Steps to reproduce: 1. neutron router-update router_id --admin_state_up=False 2. neutron router-update router_id --ha=True 3. neutron router-update router_id --admin_state_up=True 4. Tested that router namespaces created within two network nodes correctly 5. boot vm attach to the same network as router and start continuous ping, towards the router - ping replied successfully. 6. neutron router-update router_id --admin_state_up=False 7. neutron router-update router_id --ha=False 8. neutron router-update router_id --admin_state_up=True 9. Ping continue to work when router's namspaces don't part of the Ha-network anymore 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-2016:1287 |