cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Boris Stoyanov <>
Subject Re: [Discuss] 4.10: VR don't come up on Physical KVM host - possible blocker for 4.10
Date Mon, 13 Mar 2017 19:07:44 GMT
Hi Guys,

Thanks to Will Stevens we’ve managed to identify that the changes in 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 before the changes and was able to start the
VR with this commit:

I guess we’ll need to create separate PR to address fixing this issue, and refactor the
StrongSwan changes, so that it works with physical KVM hosts. I’ll be happy to assist with
testing these changes.

Boris Stoyanov
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

On Mar 7, 2017, at 12:21 PM, Boris Stoyanov <<>>

Hello everyone,

We’ve hit this issue:

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 a change that went in there that is causing this.
Currently this issue is logged as Critical and I’m suggesting we escalate it to Blocker,
as it is blocking the user to deploy a VM on a KVM physical host.

Does anyone recall any change that might have caused this?

Please find the logs attached and further details in the bug.

Boris Stoyanov<><>
53 Chandos Place, Covent Garden, London  WC2N 4HSUK

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message