[
https://issues.apache.org/jira/browse/CLOUDSTACK-9491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15689421#comment-15689421
]
ASF subversion and git services commented on CLOUDSTACK-9491:
-------------------------------------------------------------
Commit b449351a9f464cfeec90660ccc4ab8f7e547a27c in cloudstack's branch
refs/heads/4.9 from [~muralireddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b449351 ]
CLOUDSTACK-9491: incorrect parsing of device list to find ethernet index of
plugged NIC
In VmwareResource, findRouterEthDeviceIndex() method find ethernet interface
index given
the mac address. This method is used, once a nic is plugged to determine
ethernet interface.
"/proc/sys/net/ipv4/conf" from the VR and looped through the devices to find
the right
ethernet interface. However current logic read it once, and loops through the
device list.
Its observerd device may not show up '/proc/sys/net/ipv4/conf' immediatly
once NIC is plugged
in the VM from vCenter.Fix ensured, while waiting for 15 sec in the loop,
read the latest
content from /proc/sys/net/ipv4/conf, so that right device list is processed.
> 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)
