cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CLOUDSTACK-4056) System VMs are connected to untagged Management Port Group on ESX when a Tagged Management Port Group is created
Date Wed, 07 Aug 2013 18:47:24 GMT

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

Animesh Chaturvedi updated CLOUDSTACK-4056:
-------------------------------------------


These blockers and critical issues are resolved but not verified. Reporters of these issues
please verify the fixes and help close these issues
                
> System VMs are connected to untagged Management Port Group on ESX when a Tagged Management
Port Group is created
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4056
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4056
>             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
>            Reporter: Ahmad Emneina
>            Assignee: Anthony Xu
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Management Network Port group is VLAN tagged on vSwitch0.
> After creating an advanced Zone and enabling it CloudStack created 2 private port-groups
on vSwitch0 (management vSwitch), one tagged with correct VLAN (same VLAN ID as the management
network port group) and one untagged private port group without any VLAN ID..but for some
reason system VM private NICs are connected to the untagged port group, which fails connect
to CloudStack and the setup was staled (until we manually added the VLAN ID to the port group,
which was removed later somehow).

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

Mime
View raw message