[ https://issues.apache.org/jira/browse/CLOUDSTACK-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305197#comment-15305197 ]
ASF GitHub Bot commented on CLOUDSTACK-9175: -------------------------------------------- Github user bvbharatk commented on the pull request: https://github.com/apache/cloudstack/pull/1257#issuecomment-222292187 ### ACS CI BVT Run **Sumarry:** Build Number 70 Hypervisor xenserver NetworkType Advanced Passed=73 Failed=0 Skipped=3 _Link to logs Folder (search by build_no):_ https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0 **Failed tests:** **Skipped tests:** test_vm_nic_adapter_vmxnet3 test_static_role_account_acls test_deploy_vgpu_enabled_vm **Passed test suits:** test_deploy_vm_with_userdata.py test_affinity_groups_projects.py test_portable_publicip.py test_vpc_vpn.py test_over_provisioning.py test_global_settings.py test_scale_vm.py test_service_offerings.py test_routers_iptables_default_policy.py test_routers.py test_reset_vm_on_reboot.py test_snapshots.py test_deploy_vms_with_varied_deploymentplanners.py test_login.py test_list_ids_parameter.py test_public_ip_range.py test_multipleips_per_nic.py test_regions.py test_affinity_groups.py test_network_acl.py test_pvlan.py test_volumes.py test_nic.py test_deploy_vm_root_resize.py test_resource_detail.py test_secondary_storage.py test_vm_life_cycle.py test_disk_offerings.py > [VMware DRS] Adding new host to DRS cluster does not participate in load > balancing > ---------------------------------------------------------------------------------- > > Key: CLOUDSTACK-9175 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9175 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the > default.) > Components: Management Server, VMware > Affects Versions: 4.5.2 > Reporter: Suresh Kumar Anaparti > Assignee: Suresh Kumar Anaparti > > When a new VMware host is added into a cluster, Cloudstack, by default, > doesn't create all the port groups present in the cluster. And since it > doesn't have all the necessary networking port groups (existing VM's port > groups) it is not eligible to participate in DRS load balancing or HA. > Steps: > 1. Have a DRS and HA cluster in fully automated mode, with two hosts H1 and > H2 created in the vCenter. > 2. Configure this cluster in Cloudstack and create couple of VMs. > 3. Start stressing the host by running some cpu hogging scripts in each of > the VM. > 4. Enable maintenance mode on one of the host - say H1 from Cloudstack. > 5. Also, quickly enable maintenance mode on host H1 from vCenter. > (This should migrate all the VMs to host H2) Make sure none of the VMs are > present on host H1. > 6. Add host H3 into DRS cluster from vCenter and from Cloudstack as well. > 7. At this point, the load is definitely imbalanced. This can be verified > from vCenter ( Click on cluster -> Go to Summary tab -> under vSphere DRS > section, it should show 'Load imbalanced' > Now, as per DRS rules, the load should be balanced across all the available > hosts. > In this case, even after adding new host, the load is imbalanced. > The reason for the load imbalance is VMs (created from Cloudstack) are not > eligible to migrate to new host because networks or the cloud portgroups are > not available on the new host H3 (except for private). -- This message was sent by Atlassian JIRA (v6.3.4#6332)