Bug 1292527 - Backport: Support migration of non-HA router to HA and reverse
Summary: Backport: Support migration of non-HA router to HA and reverse
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 7.0 (Kilo)
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: 7.0 (Kilo)
Assignee: John Schwarz
QA Contact: Toni Freger
URL:
Whiteboard:
: 1292526 (view as bug list)
Depends On:
Blocks: 1295690
TreeView+ depends on / blocked
 
Reported: 2015-12-17 17:08 UTC by Anderson Kaiser
Modified: 2023-02-22 23:02 UTC (History)
10 users (show)

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>
Clone Of:
: 1295690 (view as bug list)
Environment:
Last Closed: 2016-06-22 19:16:48 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1365426 0 None None None 2015-12-17 17:10:23 UTC
OpenStack gerrit 233646 0 None None None 2015-12-18 04:38:19 UTC
OpenStack gerrit 262740 0 None None None 2016-01-04 12:55:06 UTC
Red Hat Product Errata RHBA-2016:1287 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2016-06-22 23:15:15 UTC

Description Anderson Kaiser 2015-12-17 17:08:40 UTC
Description of problem:

We are testing the migration from IceHouse to Kilo in our lab.

We tried to migrate our legacy routers (non-HA) to HA following the instructions on: http://docs.openstack.org/networking-guide/migration_legacy_to_L3_HA.html

So we do:
neutron router-update router_id --admin_state_up=False --- works

neutron router-update router_id --ha=True --- Fail with the message:  Cannot update read-only attribute ha

Then we find this bug: https://bugs.launchpad.net/neutron/+bug/1365426 and we apply manually the code on our envinronment and this works.

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:

neutron router-update router_id --admin_state_up=False --- works

neutron router-update router_id --ha=True --- Fail with the message:  Cannot update read-only attribute ha

Actual results:

Router attibutes can not be changed.

Expected results:

Routers should be able to migrate or change the attribute

Additional info:

Customer wants to know if this bug will be backported. He already tested it in non production and the proposed patch worked as expected.

Comment 2 Anderson Kaiser 2015-12-17 17:12:07 UTC
*** Bug 1292526 has been marked as a duplicate of this bug. ***

Comment 3 Assaf Muller 2015-12-18 04:35:43 UTC
I'm assuming you expect this backport to OSP 7, seeing as HA routers didn't exist in OSP 5?

Comment 9 Mike McCune 2016-03-28 22:49:28 UTC
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions

Comment 10 Assaf Muller 2016-06-04 19:57:20 UTC
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 '?'.

Comment 12 Toni Freger 2016-06-22 10:40:53 UTC
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

Comment 14 errata-xmlrpc 2016-06-22 19:16:48 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-2016:1287


Note You need to log in before you can comment on or make changes to this bug.