rhtyd opened a new issue #2789: Incorrect routing behaviour for link-local interface seen in XenServer/VPC VR URL: https://github.com/apache/cloudstack/issues/2789 VPC VR on XenServer (7.0) fails to start after changing of system offering for the router. On investigation it was found that packets in the VR for eth0 (link-local interface) get routed to eth1 instead of eth0. This is due to incorrect eth1 routing table rules in `Table_eth0` in the VR, the current workaround is to: (1) use a system/router offering as part of the vpc/network offering so admin don't need to change it after deploying a VPC, (2) after VR is started remove eth1 related default routes in the `Table_eth0` table. The more appropriate fix will go into `update_config.py` and other `cs` modules which configure routes for an interface. The routing table should be appropriately configured. `fwmark` should be setup for eth0 linking table 0 (Table_eth0) so packets from eth0, are routed back to eth0 for the 169.254.0.0/16 destination. ##### ISSUE TYPE * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ VR ~~~ ##### CLOUDSTACK VERSION ~~~ 4.11.1.0 ~~~ ##### CONFIGURATION Adv networking, XenServer 7.0, VPC. ##### 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. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ - Deploy a VPC VR with default offering - Create a new system offering for router - Stop VPC VR, change to the new system offering for router - Start the VR, it fails (ip_association related json application fails due to ssh timeout issue) ~~~ ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ VR should start! ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ VR fails to start ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
