cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anshul Gangwar (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-6663) [Hyper-V] Agent fails to start on some setups if last nic on host in nic list doesn't contain unicast address
Date Tue, 27 May 2014 09:07:01 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Anshul Gangwar updated CLOUDSTACK-6663:
---------------------------------------

    Status: Reviewable  (was: In Progress)

> [Hyper-V] Agent fails to start on some setups if last nic on host in nic list doesn't
contain unicast address
> -------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6663
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6663
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>            Priority: Critical
>
> Before starting Hyper-V agent we initialize HypervResourceController. We try to initialize
it with IP address 0.0.0.0. We try to get nic info of 0.0.0.0. To get nic info we iterate
through all nics and return the last NIC in  the list if it doesn't match with any IP address.
So in case last NIC doesn't have unicastAddress, Hyper-V agent will fail to start.
> We don't need IP address during initialization. It get initialized with startupcommand
later



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message