PaulAngus opened a new issue #2631: New vmware.ports.per.dvportgroup global setting breaks existing deployments URL: https://github.com/apache/cloudstack/issues/2631 <!-- Verify first that your issue/request is not already reported on GitHub. Also test if the latest release and master branch are affected too. Always add information AFTER of these HTML comments, but no need to delete the comments. --> ##### ISSUE TYPE <!-- Pick one below and delete the rest --> * Bug Report ##### COMPONENT NAME <!-- Categorize the issue, e.g. API, VR, VPN, UI, etc. --> ~~~ Hypervisor (VMware) ~~~ ##### CLOUDSTACK VERSION <!-- New line separated list of affected versions, commit ID for issues on master branch. --> ~~~ 4.11.0 ~~~ ##### CONFIGURATION <!-- --> dvSwitch in VMware environment >5.0 ##### OS / ENVIRONMENT <!-- dvSwitch in VMware environment >5.0 --> ##### SUMMARY <!-- Explain the problem/feature briefly --> ~~~ commit: https://github.com/sureshanaparti/cloudstack/commit/deb2f530b71c1dc13665c0b8dacfb025c38f58b9#diff-2e10685e0f701ef7fd43267f2879bb8e sets vmware.ports.per.dvportgroup to a low value allowing autogrow to set the value going forward. However, If a portgroup already exists and has more than (say) 10 ports in use already then a error such as: > Cannot set number of ports to 10 because at least 11 out of 18 ports are still in use will be thrown when creating a VM on said dvSwitch and the VM will fail to be deployed. Setting ALL dvsportgroups to use a sufficiently high number to cover ALL dvsportgroup values will be expensive in large environments. ~~~ ##### STEPS TO REPRODUCE <!-- For bugs, show exactly how to reproduce the problem, using a minimal test-case. Use Screenshots if accurate. For new features, show how the feature would be used. --> <!-- Paste example playbooks or commands between quotes below --> ~~~ Create a VMware environment >5.0 (5.5 in this case), which uses dvSwitches - this example manifests itself on the mgmt network. CloudStack version 4.6 use the environment sufficiently to create more than 10 ports on mgmt dvSwitch (or any other network to create other failures). Upgrade to ACS 4.11.0 Attempt to destroy CPVM in order for it to be recreated. ~~~ <!-- You can also paste gist.github.com links for larger files --> ##### EXPECTED RESULTS <!-- What did you expect to happen when running the steps above? --> ~~~ CPVM is destroyed and recreated (CloudStack either leaves number of ports attached 'as is' or reduces the number of ports in the portgroup to slightly greater than the number of ports in use. ~~~ ##### ACTUAL RESULTS <!-- What actually happened? --> <!-- Paste verbatim command output between quotes below --> ~~~ An error is thrown: > Cannot set number of ports to 10 because at least 11 out of 18 ports are still in use CPVM is not deployed. ~~~
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
