[
https://issues.apache.org/jira/browse/CLOUDSTACK-9683?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15768963#comment-15768963
]
ASF GitHub Bot commented on CLOUDSTACK-9683:
--------------------------------------------
Github user abhinandanprateek commented on the issue:
https://github.com/apache/cloudstack/pull/1839
@rhtyd most of the automation environments are single hypervisor one, so
will end up creating a mixed hypervisor zone for this test only. If that can be
done i can put one together, probably not worth the effort. @borisstoyanov
> system.vm.default.hypervisor Does Not Pin Hypervisor Type of Virtual Routers
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9683
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9683
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0.1
> Reporter: Abhinandan Prateek
> Assignee: Abhinandan Prateek
> Fix For: 4.9.2.0
>
>
> The system.vm.default.hypervisor global setting should pin the type of
> hypervisor on which VRs are created. Therefore, if a user VM is created in a
> VMware cluster with a new isolated network, the associated VR should be
> created on a KVM host. However, the VR is being created on the same
> hypervisor as the user VM instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
