Chandan Purushothama created CLOUDSTACK-281:
-----------------------------------------------
Summary: On Updating the VMWare Traffic Labels of existing
Physical Networks to Invalid Values; Triggering a ReconnectHost Command,
successfully reconnected the ESXi host instead of reporting an Alert
Key: CLOUDSTACK-281
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-281
Project: CloudStack
Issue Type: Bug
Components: Management Server
Affects Versions: 4.1.0
Reporter: Chandan Purushothama
Fix For: 4.1.0
=========
Use Case:
=========
Update Traffic Labels of existing Physical networks to Invalid values
================
Steps to Reproduce:
================
1. Deploy an Advanced Zone Setup with Two Physical Networks. One Physical
Network has guest,management,public,storage traffic while the other physical
network has guest traffic only. The Setup has one ESXi 5.0 Cluster.
2. All the Traffic Labels of Physical Network 1 are given as vSwitch0 and
Traffic label of Physical Network 2 is given as vSwitch1.
i) PhyNet1
- Mgmt,public,Storage,Guest (Traffic label = vSwitch0)
ii) PhyNet2
- Guest (Traffic label = vSwitch1)
3. Deploy Guest VMs using above physical networks
4. Change traffic labels of each traffic type to different values that do not
exist on hypervisor (Ex: vSwitch0 to vSwitch2 and vSwitch1 to vSwitch3).
5. Issue a ReconnectHost request to the ESXi 5.0 Host.
6. Observe that the Host Successfully reconnects back after a while in spite of
wrong traffic labels
===========
Git Info:
===========
Git Revision: c69ad1784328cfed1a2ecb64780b8efcb6a2e68e
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
--
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
