You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/06/25 16:16:20 UTC

[jira] [Commented] (CLOUDSTACK-1767) VMWare DVS - cannot use untagged portgroups

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

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

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

CLOUDSTACK-1767 VMWare DVS - cannot use untagged portgroups

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

                
> VMWare DVS - cannot use untagged portgroups
> -------------------------------------------
>
>                 Key: CLOUDSTACK-1767
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1767
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server, VMware
>    Affects Versions: 4.2.0
>         Environment: 4.2 Master
>            Reporter: ilya musayev
>            Assignee: Sateesh Chodapuneedi
>            Priority: Critical
>              Labels: CLOUDSTACK, DVS, VMWARE
>             Fix For: 4.2.0
>
>
> Please revise this portion of the code in vmware-base/src/com/cloud/hypervisor/vmware/mo/HypervisorHostHelper.java 
> if (vid != null) { 
>      vlanSpec = createDVPortVlanIdSpec(vid); 
>   } else { 
>      vlanSpec = createDVPortVlanSpec(); 
> } 
> This code does not take into account PortGroups on DVS that are untagged. This issue was particularly hard to identify as stack trace would only show up on the hypervisor hostd.log and VC error is was vary vague. the hostd.log on hypervisor indicate that vlanSpec is invalid for PortGroups that are untagged (or the ID is left blank). 
> 2013-03-14T20:32:12.351Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Throw vim.fault.DvsApplyOperationFault 
> 2013-03-14T20:32:12.352Z [41D16B90 info 'Vmomi' opID=786a44c8-8d] Result: 
> --> (vim.fault.DvsApplyOperationFault) { 
> --> dynamicType = <unset>, 
> --> faultCause = (vmodl.MethodFault) null, 
> --> objectFault = (vim.fault.DvsApplyOperationFault.FaultOnObject) [ 
> --> (vim.fault.DvsApplyOperationFault.FaultOnObject) { 
> --> dynamicType = <unset>, 
> --> objectId = "2442", 
> --> type = "vim.dvs.DistributedVirtualPort", 
> --> fault = (vmodl.fault.InvalidArgument) { 
> --> dynamicType = <unset>, 
> --> faultCause = (vmodl.MethodFault) null, 
> --> invalidProperty = "vlanSpec", 
> --> msg = "", 
> --> }, 
> --> } 
> --> ], 
> --> msg = "", 
> --> } 

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