[R2.2 46] BGP Peering doesn't happen when ibgp_auto_mesh is enabled.

Bug #1463771 reported by asbalaji
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
R2.20
Fix Committed
Critical
Sachin Bansal
Trunk
Fix Committed
Critical
Sachin Bansal

Bug Description

BGP Peering doesn't happen when ibgp_auto_mesh is enabled.

Schema generator is not setting bgp router refs for all control nodes.

Sanity is explicitly setting bgp router refs for all provisioned control nodes (provision_bgp) so the issue is not seen in sanity.

Peering happens when we disable this flag and explicitly setting peers. Observed this behaviour in both UI and REST API calls.

Also, the 'autonomous_system' tag in 'global-system-config' is seen as a string (should be an integer as per schema) in 'defaults' (provision_control.py) when system comes up initially.
 defaults = {
            'router_asn': '64512',
            'ibgp_auto_mesh': None,
            'api_server_ip': '127.0.0.1',
            'api_server_port': '8082',
            'oper': None,
            'admin_user': None,
            'admin_password': None,
            'admin_tenant_name': None
        }

Tags: blocker config
asbalaji (asbalaji)
Changed in juniperopenstack:
milestone: none → r2.30-fcs
summary: - BGP Peering doesnt happen when ibgp_auto_mesh is enabled.
+ [R2.2 46] BGP Peering doesn't happen when ibgp_auto_mesh is enabled.
asbalaji (asbalaji)
description: updated
information type: Proprietary → Public
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/11514
Submitter: Sachin Bansal (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] R2.20

Review in progress for https://review.opencontrail.org/11516
Submitter: Sachin Bansal (<email address hidden>)

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : A change has been merged

Reviewed: https://review.opencontrail.org/11514
Committed: http://github.org/Juniper/contrail-controller/commit/a45e7e316af1462815906e79cff504d73f8ec825
Submitter: Zuul
Branch: master

commit a45e7e316af1462815906e79cff504d73f8ec825
Author: Sachin Bansal <email address hidden>
Date: Thu Jun 11 11:17:40 2015 -0700

Fix multiple issues with ibgp auto mesh

1. vendor name was not being initialized
2. router asn change and global asn change need to be handled differently
3. create peering among all routers with asn same as global

Change-Id: I1589e10ece9575f935b9e78ca1d6f41192dc1463
Closes-Bug: 1463771

Revision history for this message
OpenContrail Admin (ci-admin-f) wrote :

Reviewed: https://review.opencontrail.org/11516
Committed: http://github.org/Juniper/contrail-controller/commit/aaab87c3f067a2824e2a11dd7d5794620bf456a5
Submitter: Zuul
Branch: R2.20

commit aaab87c3f067a2824e2a11dd7d5794620bf456a5
Author: Sachin Bansal <email address hidden>
Date: Thu Jun 11 11:17:40 2015 -0700

Fix multiple issues with ibgp auto mesh

1. vendor name was not being initialized
2. router asn change and global asn change need to be handled differently
3. create peering among all routers with asn same as global

Change-Id: I1589e10ece9575f935b9e78ca1d6f41192dc1463
Closes-Bug: 1463771
(cherry picked from commit f5e5450dba0bc27961c95f44fa174134602e5310)

Nischal Sheth (nsheth)
tags: removed: contrail-control
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.