ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
mgmt server is in Pod1/subnet1,
hypervisor (and thus VR's control NIC) is in Pod2/subnet2 - thus there is a routing process between mgmt and VR's NIC IP
OS / ENVIRONMENT
Probably affects only VMware, but has not been tested with XS/KVM (should not be a problem, but needs checking)
SUMMARY
Only VPC VR affected (VR for shared or simpler Isolated network is NOT affected).
There is a patching error of the VPC VR (this might be a problem or a consequence of missing routes) - either way, route from VR to the subnet of the mgmt server (subnet1) is missing/not configured, and thus VR can't talk to the mgmt server - VR configuration never completes. CMDLINE looks fine (all parameters look fine) but things are not applied correctly on the OS level.
STEPS TO REPRODUCE
For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate.
For new features, show how the feature would be used.
mgmt server in subnet1, hypervisor (and thus VR's control NIC) in subnet2 - so that VR needs to send packet to the Pod2's gateway in order to reach Pod1/mgmt server.
EXPECTED RESULTS
VR patched up and operational
ACTUAL RESULTS
VR not patched, routes not present as needed.
CMD line of the VPC VR:

cloud.log

Routing table empty (there should be multiple routes (route to the mgmt cidr should be via 10.1.32.1 for 10.1.32.0 network - see CMDLINE output)

ISSUE TYPE
COMPONENT NAME
CLOUDSTACK VERSION
CONFIGURATION
mgmt server is in Pod1/subnet1,
hypervisor (and thus VR's control NIC) is in Pod2/subnet2 - thus there is a routing process between mgmt and VR's NIC IP
OS / ENVIRONMENT
Probably affects only VMware, but has not been tested with XS/KVM (should not be a problem, but needs checking)
SUMMARY
Only VPC VR affected (VR for shared or simpler Isolated network is NOT affected).
There is a patching error of the VPC VR (this might be a problem or a consequence of missing routes) - either way, route from VR to the subnet of the mgmt server (subnet1) is missing/not configured, and thus VR can't talk to the mgmt server - VR configuration never completes. CMDLINE looks fine (all parameters look fine) but things are not applied correctly on the OS level.
STEPS TO REPRODUCE
EXPECTED RESULTS
ACTUAL RESULTS
CMD line of the VPC VR:

cloud.log

Routing table empty (there should be multiple routes (route to the mgmt cidr should be via 10.1.32.1 for 10.1.32.0 network - see CMDLINE output)