Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1153446

Summary: [RFE][neutron]: Report HA Router Master
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: openstack-neutronAssignee: Assaf Muller <amuller>
Status: CLOSED ERRATA QA Contact: Roey Dekel <rdekel>
Severity: medium Docs Contact:
Priority: high    
Version: unspecifiedCC: chrisw, markmc, mlopes, nyechiel, oblaut, tfreger, yeylon
Target Milestone: gaKeywords: FutureFeature
Target Release: 7.0 (Kilo)   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/neutron/+spec/report-ha-router-master
Whiteboard: upstream_milestone_kilo-rc1 upstream_definition_approved upstream_status_implemented
Fixed In Version: Doc Type: Enhancement
Doc Text:
With this update, administrators are now able to view the state of High Availability routers on each node, and specifically, where the active instance is hosted. Previously, the High Availability router state information was not visible to the administrator; this made maintenance harder, for example, when moving HA router instances from one agent to another, or assessing the impact of putting a node in maintenance mode. This new functionality also serves as a sanity test and offers assurance that a router is indeed active on only one node. As a result, administrators may now run the 'neutron l3-agent-list-hosting-router <router_id>' command on a High Availability router to view where the active instance is currently hosted.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-08-05 13:14:54 UTC Type: ---
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: 1215475    

Description RHOS Integration 2014-10-16 04:05:40 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/report-ha-router-master.

Description:

Highly available routers is a new functionality that was merged in the
l3-high-availability blueprint. HA routers are scheduled on multiple L3 agents
however the cloud operator has no way of knowing where the active instance
is.

Specification URL (additional information):

None

Comment 4 Roey Dekel 2015-06-08 13:58:41 UTC
Verified on Kilo with:

Version-Release number of selected component:
---------------------------------------------
Puddle: 2015-06-02.1
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-common-2015.1.0-1.el7ost.noarch
openstack-neutron-2015.1.0-1.el7ost.noarch
python-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-ml2-2015.1.0-1.el7ost.noarch

Reproduce steps:
----------------
1. Set up VRRP environment
2. Add an ha router
3. neutron l3-agent-list-hosting-router router1
4. Compare to state at the networkers

Results:
--------
As expected:

[root@controller ~(keystone_admin)]# neutron l3-agent-list-hosting-router router1
+--------------------------------------+---------------------+----------------+-------+----------+
| id                                   | host                | admin_state_up | alive | ha_state |
+--------------------------------------+---------------------+----------------+-------+----------+
| 348dfa4a-c9f8-418a-9975-2fbd0bca8562 | network-3.novalocal | True           | :-)   | active   |
| c3460556-4e4b-4724-b79e-4870ab517e8b | network-1.novalocal | True           | :-)   | standby  |
| 835fe946-5c08-415e-b88e-4fd7144c847d | network-2.novalocal | True           | :-)   | standby  |
+--------------------------------------+---------------------+----------------+-------+----------+

[root@controller ~(keystone_admin)]# for i in `seq 185 187`; do ssh root.186.$i 'cat /var/lib/neutron/ha_confs/fe56731b-90f3-4a57-b3a5-540794f6d187/state'; echo ' '; done
backup 
backup 
master

Comment 6 errata-xmlrpc 2015-08-05 13:14:54 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/RHEA-2015:1548