[5.0 VRO]policy rules not getting applied to attahed VNs

Bug #1756289 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
Daniel Jasiński

Bug Description

Scenario:Create policy p1 and attach p1 to two vns
Rules: pass protocol any network any ports any <> network any ports any
ping between vms on these networks

workflows
Create Network Policy
Add rule to Network policy
Add network policy to virtual network

schema is discrading the rules as there are no rule sequence numbers and
rules are not getting in to effect on the VNs and
so ping bewteen vms is failing

below is the diff for policy created from workflow and contrail UI

Rules created from workflow Add rule to Network policy

virtual_network_back_refs: [
{
to: [
"default-domain",
"admin",
"aswin-vn2"
],
href: "http://10.204.217.209:8082/virtual-network/8b127b70-1cd8-4274-ae8d-fad43980df40",
attr: { },
uuid: "8b127b70-1cd8-4274-ae8d-fad43980df40"
},
{
to: [
"default-domain",
"admin",
"aswin-vn1"
],
href: "http://10.204.217.209:8082/virtual-network/bfb9ebef-7259-491d-8db9-5f6c67ca58b9",
attr: { },
uuid: "bfb9ebef-7259-491d-8db9-5f6c67ca58b9"
}
],

policy and Rules created from contrail-ui which has major and minor rule sequences

virtual_network_back_refs: [
{
to: [],
href: "http://10.204.217.209:8082/virtual-network/8b127b70-1cd8-4274-ae8d-fad43980df40",
attr: {
timer: null,
sequence: {
major: 1,
minor: 0
}
},
uuid: "8b127b70-1cd8-4274-ae8d-fad43980df40"
},
{
to: [],
href: "http://10.204.217.209:8082/virtual-network/bfb9ebef-7259-491d-8db9-5f6c67ca58b9",
attr: {
timer: null,
sequence: {
major: 1,
minor: 0
}
},
uuid: "bfb9ebef-7259-491d-8db9-5f6c67ca58b9"
}
],

Tags: vmware
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.