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

ASF GitHub Bot commented on CLOUDSTACK-9811:
--------------------------------------------

GitHub user ustcweizhou opened a pull request:

    https://github.com/apache/cloudstack/pull/2011

    CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name 
p<slot_number>p<port_number>

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/ustcweizhou/cloudstack fix-issue-p55p1

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/2011.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #2011
    
----
commit cf442b459ae79ff7828c0ae868c4e1af9c078f01
Author: Wei Zhou <w.z...@tech.leaseweb.com>
Date:   2017-03-16T10:48:35Z

    CLOUDSTACK-9811: fix duplicated nics on VR caused by nic name 
p<slot_number>p<port_number>

----


> 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)

Reply via email to