Static Route creation fails on VPC with working Private Gateways — Hub & Spoke topology

[muthukrishnang1100]

I am setting up a Hub and Spoke VPC topology on CloudStack 4.22 single node KVM deployment. I created three VPCs and connected them using transit networks with private gateways. All private gateways are showing Ready state and VR-to-VR connectivity across the transit networks is working fine. However, when I try to add static routes to the VPCs via the UI to enable routing between the VPCs, I get a generic "Failed to create static route" error with no further details. The management server log does not show any specific static route error either. As a workaround I manually added routes inside the Virtual Routers via virsh console and confirmed that routes are being installed correctly, and traceroute shows packets successfully reaching the remote VPC's Virtual Router transit interface — but packets are getting dropped before reaching the destination VM. We suspect the issue may be related to iptables FORWARD rules on the VPC Virtual Router blocking inter-VPC forwarded traffic. Has anyone successfully implemented Hub and Spoke VPC routing on CloudStack 4.22? Is the static route UI failure a known bug, and is there a recommended way to make inter-VPC routes persistent across VR restarts?

[weizhouapache]

it looks like you are hitting the issue #12672 which is fixed by #11967