[R5.1 build 345]Creation of routing policy with extended community parameters is failing

Bug #1803493 reported by aswani kumar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Juniper Openstack
Status tracked in Trunk
Trunk
Fix Committed
Critical
Nikhil Bansal

Bug Description

5.1 Build 345
Creation of routing policy with extended community is failing with below error

There was an issue with the request. Error Code 400
Bad property in http_put: Error validating property routing_policy_entries value {'term': [{'term_match_condition': {'protocol': ['interface'], 'community_list': [], 'prefix': [], 'extcommunity_match_all': False, 'community_match_all': False, 'extcommunity_list': ['accept-own']}, 'term_action_list': {'update': {'extcommunity': {'add': {'community': ['target:64512:1']}, 'set': {'community': [None]}, 'remove': {'community': [None]}}}}}]} Invalid community format target:64512:1. Change to 'number:number'

Tags: blocker
tags: added: blocker
Revision history for this message
OpenContrail Admin (ci-admin-f) wrote : [Review update] master

Review in progress for https://review.opencontrail.org/47689
Submitter: Nikhil 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/47689
Committed: http://github.com/Juniper/contrail-api-client/commit/0b7788ac8161d6e44f398753ed052f39fd64fc4f
Submitter: Zuul v3 CI (<email address hidden>)
Branch: master

commit 0b7788ac8161d6e44f398753ed052f39fd64fc4f
Author: Nikhil Bansal <email address hidden>
Date: Thu Nov 15 15:07:26 2018 +0530

extcommunity needs separate type in schema

I had reused the type that was used for community for ext-community
also but it seems that backend has special treatment for CommunityListType.
It expects the format to be number:number format.

Change-Id: I793de9ad115360d866150a2c9fb0887d3cadd2d0
Closes-Bug: #1803493

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.