Re: [Discuss] 4.10: VR don't come up on Physical KVM host - possible blocker for 4.10

2017-03-13 Thread Will Stevens
Boris, please test this PR in your environment: https://github.com/apache/cloudstack/pull/2003 Thanks, *Will Stevens* On Mon, Mar 13, 2017 at 3:35 PM, Will Stevens wrote: > I will open a PR to update the offending line of code to be more defensive > so it won't error. We can't revert that c

Re: [Discuss] 4.10: VR don't come up on Physical KVM host - possible blocker for 4.10

2017-03-13 Thread Will Stevens
I will open a PR to update the offending line of code to be more defensive so it won't error. We can't revert that change because it will re-introduce a bug which causes the source nat IP to not be the primary IP on the nic after a VR reboot. I will open a PR to fix this right now so you can test

Re: [Discuss] 4.10: VR don't come up on Physical KVM host - possible blocker for 4.10

2017-03-13 Thread Boris Stoyanov
Hi Guys, Thanks to Will Stevens we’ve managed to identify that the changes in cs_ip.py introduced in StrongSwan development were causing this blocker. I guess it managed to slip in, since it appears only on physical KVM hosts. I’ve reverted back to the state of cs_ip.py before the changes and w

[Discuss] 4.10: VR don't come up on Physical KVM host - possible blocker for 4.10

2017-03-07 Thread Boris Stoyanov
Hello everyone, We’ve hit this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-9811 On our physical hosts environment we’re not able to start the VR, it appears that it’s looking for eth3 configuration but no such is available. We’ve narrowed down the issue only to 4.10, so it must been