Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 13 Mar 2017 19:02:41 +0000 (UTC)
From: "Boris Stoyanov (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13047671.1488460564000.5610.1489431761747@Atlassian.JIRA>
In-Reply-To: <JIRA.13047671.1488460564000@Atlassian.JIRA>
References: <JIRA.13047671.1488460564000@Atlassian.JIRA> <JIRA.13047671.1488460564481@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9811) VR will not start, looking to
 configure eth3 while no such device exists on the VR. On KVM-CentOS6.8
 physical host
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 13 Mar 2017 19:02:47 -0000


    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15922738#comment-15922738 ] 

Boris Stoyanov commented on CLOUDSTACK-9811:
--------------------------------------------

That is it [~wstevens], I've reverted the changes to https://github.com/swill/cloudstack/blob/8b4c36ef501a96742c52b4d532cc3adda25aa71b/systemvm/patches/debian/config/opt/cloud/bin/cs_ip.py
which is the previous version before StrongSwan. VR did came up and the instance got deployed. I guess we need to create a separate PR to address this issue and restructure the StronSwan changes, I'll be really happy to help with testing.


> VR will not start, looking to configure eth3 while no such device exists on the VR. On KVM-CentOS6.8 physical host
> ------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9811
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9811
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Virtual Router
>    Affects Versions: 4.10.0.0
>            Reporter: Boris Stoyanov
>            Priority: Blocker
>         Attachments: agent.log, cloud.log, management.log
>
>
> This issue appears only on 4.10. When you add an instance with a new network the VR starts and fails at the configuration point. Looks like it is looking to configure eth3 adapter while no such device should be available on the VR. 
> The VR does not start and aborts the deployment of the VM. 
> Pease note that this issue was reproduced on physical KVM hosts in our lab.
> Hardware Hosts details:
> - 4x Dell C6100
> - Using: American Megatrends MegaRAC Baseboard Management (IPMI v2 compliant)
> OS:
> CentOS 6.8. 
> Management: 
> VM, running CentOS 6.8
> ACS version: 4.10 RC 1. SHA: 7c1d003b5269b375d87f4f6cfff8a144f0608b67
> In a nested virtualization environment it was working fine with CentOS6.8. 
> Attached are the management log and the cloud.log form the VR. 


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)