Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 23 Nov 2016 08:57:58 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13003304.1473266277000.348131.1479891478955@Atlassian.JIRA>
In-Reply-To: <JIRA.13003304.1473266277000@Atlassian.JIRA>
References: <JIRA.13003304.1473266277000@Atlassian.JIRA> <JIRA.13003304.1473266277060@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-9491) Vmware resource: incorrect
 parsing of device list to find ethener index of plugged nic
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 23 Nov 2016 08:58:00 -0000


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

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

Github user rhtyd commented on the issue:

    https://github.com/apache/cloudstack/pull/1681
  
    LGTM, failures related to vpc/rvr are known intermittent failures. We'll kick another test round on #1753, #1754 etc. and work towards fixing them for vmware and xenserver separately.  Merging this based on code reviews and tests.


> Vmware resource: incorrect parsing of device list to find ethener index of plugged nic
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9491
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9491
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.6.0
>            Reporter: Murali Reddy
>            Assignee: Murali Reddy
>             Fix For: 4.10.0.0, 4.9.1.0, 4.8.2.0
>
>
> In VmwareResource.java, there is logic ( in findRouterEthDeviceIndex) to find ethernet interface a mac address is associated with.
> After NIC in plugged in to a Vm through vSphere, it takes some time for the device to show up in the guest VM.
> Logic loops through the device list obtained from /proc/sys/net/ipv4/conf from the VM, and matched againest mac.
> However '/proc/sys/net/ipv4/conf'  is not refreshed, heve logic loops through old device list always.
> In addition there is no exception thrown and error is maked by sending -1. 
> Eventually, VR scripts are getting -1 as device number causing failure in processing the scripts.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)