borisstoyanov opened a new issue #6084:
URL: https://github.com/apache/cloudstack/issues/6084
<!--
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.
-->
~~~
Router Deployment
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.16
~~~
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Having both VMware and Xen clusters
custom offering for router with host tag: xen
Have a XenServer/xcp-ng host tagged with tag: xen
system.vm.default.hypervisor = XenServer
router.service.offering = [uuid-of-custom-offering]
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When a user has 2 types of hypervisors, and he wants to create VRs on one of
the types (say Xen), he would create a host tag in the custom router offering
and tag a xen host/cluster. Then they would change the
system.vm.default.hypervisor to XenServer.
##### Steps
~~~
- set the configuration described
- deploy a vmware template in a newly created network
- observe the failure
~~~
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
deployment successful, router on xen
~~~
##### ACTUAL RESULTS
<!-- What actually happened? -->
<!-- Paste verbatim command output between quotes below -->
~~~
deployment fails, cloudstack tried to deploy an ova to xen
~~~
[vmware.log](https://github.com/apache/cloudstack/files/8221143/vmware.log)
--
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]
