Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 7 Aug 2013 18:47:42 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12639630.1364491317735.18779.1375901262442@arcas>
In-Reply-To: <JIRA.12639630.1364491317735@arcas>
References: <JIRA.12639630.1364491317735@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-1835) VMWare tries to use vSwitch0
 when it shouldn't
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi updated CLOUDSTACK-1835:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues please verify the fixes and help close these issues
                
> VMWare tries to use vSwitch0 when it shouldn't
> ----------------------------------------------
>
>                 Key: CLOUDSTACK-1835
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1835
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: VMware
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Francois Gaudreault
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: vswitch0_bug.png
>
>
> When creating a VR, CS tries creates the public VLAN on the vSwitch0 even if we told him to use vSwitch2 during the Zone setup. 
> Expected behaviour is that CS creates the port-group only where it should be, so on vSwitch2 in our case. See the snapshot included.
> From the log:
> Preparing NIC device on network cloud.public.142.0.1-vSwitch0
> INFO  [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Prepare NIC device based on NicTO: {"deviceId":4,"networkRateMbps":-1,"defaultNic":false,"ip":"0.0.0.0","netmask":"255.255.255.255","gateway":"10.0.142.1","mac":"02:00:3b:5a:00:02","dns1":"10.0.31.24","dns2":"10.0.31.28","broadcastType":"Vlan","type":"Public","broadcastUri":"vlan://142","isolationUri":"vlan://142","isSecurityGroupEnabled":false}
> INFO  [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Prepare network on vSwitch: P[vSwitch0:untagged] with name prefix: cloud.public
> INFO  [vmware.mo.HypervisorHostHelper] (DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is ready on vSwitch vSwitch0
> INFO  [vmware.mo.HypervisorHostHelper] (DirectAgent-47:yul01vi13.ops.dot) Network cloud.public.142.0.1-vSwitch0 is ready on vSwitch vSwitch0
> INFO  [vmware.resource.VmwareResource] (DirectAgent-47:yul01vi13.ops.dot) Preparing NIC device on network cloud.public.142.0.1-vSwitch0 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira