rajujith opened a new issue, #7433:
URL: https://github.com/apache/cloudstack/issues/7433
<!--
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release and main 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.
-->
~~~
VR, Deployment Planner
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.18, All before 4.18
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Any zone with more than one cluster type: XenServer, KVM, VMware
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
<!-- Explain the problem/feature briefly -->
##### 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 -->
~~~
1. Create a zone with two clusters of different hypervisor types
XenServer/VMware ESXi/KVM
2. Disable One Cluster example: VMware
3. Deploy a virtual machine and create a new guest network, now both VM and
VR are created on the XenServer/KVM cluster
4. Disable the XenServer/KVM cluster from Step 3
5. Retart the guest network with clean-up, the new virtual router fails to
get created.
(This issue appears randomly(based on the logic mentioned below), retry a
couple of times if this is not observed. )
~~~
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
The virtual router should get created
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
The virtual router fails to get created.
~~~
The same could affect SystemVMs as well, the issue is appearing due to the
current deployment logic where the new virtual router hypervisor type is
decided even before checking if there is any available/suitable host of the
same type in the zone and this won't be retried.
Example from logs:
Allocating the VR with id=6 in datacenter Zone .......with the hypervisor
type KVM
Deploy avoids pods: [], clusters: [2, 3], hosts: [] , <---- Disabled
clusters KVM & VMware
Cluster: 1 has HyperVisorType that does not match the VM, skipping this
cluster <---- XenServer Cluser
No clusters found after removing disabled clusters and clusters in avoid
list, returning.
state transited from [Starting] to [Stopped] with event [OperationFailed]
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
