Hi, We've hit a variation on an older (fixed) bug regarding VPC private gateways. The old case which prevented a restart of the VPC router (cloudstack-4193) was fixed; but this time, we could not spin up a virtual router when the VPC router was destroyed, unless the private gateway was removed from the VPC config.
The use case why we need to destroy the VPC router: we need to move the routerVM away from the cluster it is running on, since the cluster will be decomissioned. RouterVM's can't be migrated to other clusters, thus need to be destroyed to have them created on a new cluster. This issue prevents a smooth travelling of VPC routers from old to new clusters. Stack traces are in CLOUDSTACK-6448. Kind regards, Anton Opgenoort
