SYMC: Some tap interfaces are not associated with any vrf
Bug #1480613 reported by
Rudrajit Tapadar
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenContrail |
New
|
High
|
Unassigned |
Bug Description
After upgrade from 2.01-43 to 2.02-59, some IPs were not reachable. On investigating I found that some tap interfaces were not associated with their vrf's. One of them got fixed by bouncing the vrouter agent, but there are a few in which the vrf config is not getting pushed even after bouncing vrouter agent. I have tried bouncing the schema transformer as well.
Below is a sample error in the tap interface config taken from the controller. I have starred out the IP address.
fip_list: {
list: {
FloatingI
ip_addr: "*.*.*.*",
vrf_name: "--ERROR--",
installed: "N"
}
}
},
Changed in opencontrail: | |
importance: | Undecided → High |
tags: | added: vrouter |
summary: |
- Some tap interfaces are not associated with any vrf + SYMC: Some tap interfaces are not associated with any vrf |
To post a comment you must log in.