5.0: Granular Routing policy. Match based on incoming community from Bgpaas client does not work

[Shashikiran H]

Version: 5.0
Picked up the latest build.

Topo:
10.204.217.7 cfgm control ui openstack
10.204.216.68 cfgm control
10.204.216.72 cfgm control
10.204.217.16 vrouter
10.204.217.17 vrouter

bgpaas-vm -- left--- right

Routes that are reoriginated are not supported according to 1753981.
What works:
If bgpaas client sends a well known community(no-exprot etc), I can filter the routes based on well known community correctly.
<iq>
 <routing-policy-entries>
  <term>
   <term-match-condition>
    <community></community>
    <community-list>no-export</community-list>
    <community-match-all>false</community-match-all>
   </term-match-condition>
   <term-action-list>
    <update>
     <as-path>
      <expand />
     </as-path>
     <community>
      <add />
      <remove>
       <community>64512:44444</community>
      </remove>
      <set />
     </community>
     <local-pref>0</local-pref>
     <med>0</med>
    </update>
    <action></action>
   </term-action-list>
  </term>
 </routing-policy-entries>
</iq>

What does not work:
If the bgpaas client sends a route with a community value of say 64512:22222, I cant filter these routes based on explicit community match condition of 64512:22222

<iq>
 <routing-policy-entries>
  <term>
   <term-match-condition>
    <community></community>
    <community-list>64512:22222</community-list>
    <community-match-all>false</community-match-all>
   </term-match-condition>
   <term-action-list>
    <update>
     <as-path>
      <expand />
     </as-path>
     <community>
      <add />
      <remove>
       <community>64512:44444</community>
      </remove>
      <set />
     </community>
     <local-pref>0</local-pref>
     <med>0</med>
    </update>
    <action></action>
   </term-action-list>
  </term>
 </routing-policy-entries>
</iq>

[Shashikiran H (skiranh)]

Not seeing this with Nikhil's patch for other Routing policy bugs