[
https://issues.apache.org/jira/browse/CLOUDSTACK-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15682825#comment-15682825
]
ASF GitHub Bot commented on CLOUDSTACK-9491:
--------------------------------------------
Github user rhtyd commented on the issue:
https://github.com/apache/cloudstack/pull/1681
LGTM on tests, the failures wrt VPC are known intermittent issues. I'm not
sure about the internal lb failures, I'll kick another test round since there
have been several changes on the base branch.
@blueorangutan package
> 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)
