Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 27 May 2014 09:05:01 +0000 (UTC)
From: "Anshul Gangwar (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12714124.1400050735471.21339.1401181501572@arcas>
In-Reply-To: <JIRA.12714124.1400050735471@arcas>
References: <JIRA.12714124.1400050735471@arcas>
Subject: [jira] [Assigned] (CLOUDSTACK-6663) [Hyper-V] Agent fails to start
 on some setups if last nic on host in nic list doesn't contain unicast
 address
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Anshul Gangwar reassigned CLOUDSTACK-6663:
------------------------------------------

    Assignee: Anshul Gangwar

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