cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-7360) [vmware] Add host to existing cluster fails if the cluster is using Nexus 1000v as backend for atleast one traffic type.
Date Mon, 18 Aug 2014 08:49:19 GMT

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

ASF subversion and git services commented on CLOUDSTACK-7360:
-------------------------------------------------------------

Commit a1d0925f902041b187f14413e91bc368f0708753 in cloudstack's branch refs/heads/master from
[~sateeshc]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=a1d0925 ]

CLOUDSTACK-7360 [vmware] Add host to existing cluster fails if the cluster is using Nexus
1000v as backend for atleast one traffic type.

While adding host to existing cluster which is using Nexus 1000v as a network backend, skip
validation of Nexus VSM as it was already done while adding that cluster.

Signed-off-by: Sateesh Chodapuneedi <sateesh@apache.org>


> [vmware] Add host to existing cluster fails if the cluster is using Nexus 1000v as backend
for atleast one traffic type.
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7360
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7360
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.2.0, 4.3.0, 4.4.0
>         Environment: vCenter/ESXi 5.0, Nexus 1000v 1.4
>            Reporter: Sateesh Chodapuneedi
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.5.0
>
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> Steps to reproduce:
> 1) Before creating zone, set global params vmware.use.nexus.vswitch & vmware.use.dvswitch
is to "true".
> 2) Complete zone wizard
> 3) Using vCenter add ESXi host to a cluster, which is already being managed by CCP
> 4) Using CCP UI add the same host to that cluster - This fails



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

Mime
View raw message