I identified a bug in kolla-ansible where the routing and rule tables would change at container restart, polluting the routing table on the network node.
Now I can see a little farther into the stack. On the network node, I can reach everything on 10.197.0.0/25 just fine; however, there is no route announced to FRR.
As a workaround, I added an address of 10.197.0.1/25 to bgp-nic.
Once I did that, the network was announced and I could reach everything. However after a sync, this goes away.
The issue appears that we are missing that particular item to complete this.
I identified a bug in kolla-ansible where the routing and rule tables would change at container restart, polluting the routing table on the network node.
Now I can see a little farther into the stack. On the network node, I can reach everything on 10.197.0.0/25 just fine; however, there is no route announced to FRR.
As a workaround, I added an address of 10.197.0.1/25 to bgp-nic.
Once I did that, the network was announced and I could reach everything. However after a sync, this goes away.
The issue appears that we are missing that particular item to complete this.