tbudx opened a new issue, #7101:
URL: https://github.com/apache/cloudstack/issues/7101
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
Network offering
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
4.17.1.0, 4.17.2.0, earlier versions not tested
##### CONFIGURATION
<!--
Information about the configuration if relevant, e.g. basic network,
advanced networking, etc. N/A otherwise
-->
Advanced zone
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
Management server: CentOS 8.8
VMware version: 6.7
##### SUMMARY
<!-- Explain the problem/feature briefly -->
Creating a custom Network offering for isolated and/or shared networks with
a set of supported services and a Compute offering definition for the VR
provider results in the Compute offering being ignored. This only applies to
the custom Network definition created using the web interface. Using the
appropriate API (createNetworkOffering) with specifying the serviceOfferingID
works.
As a result of this the corresponding VR is created with the default service
offering and not attached to the appropriate network. Also not honoring host
tags, etc.
##### 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 System offering for type "Domain router", use host tags and
storage tags to allow for workload separation. Hypervisor used is VMware.
2. Create a custom Network offering. Isolated. Pick necessary services to be
enabled on VR and select the previously created System (Compute) offering
3. Create a new Guest network (isolated) using the previously defined
Network offering
4. Create a Compute Instance attached to the previously created Network,
with host and storage tags for workload separation.
<!-- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
1. Compute Instance created and running on the chosen network
2. VR created and also attached on the selected network, providing requested
services and using the System offering associated with the Network/Network
offering.
##### ACTUAL RESULTS
<!-- What actually happened? -->
1. Compute instance created and running on the selected network, on host
matching host tags.
2. VR created and started, however, ignoring the Compute offering associated
with the network offering and Network. Therefore, started on wrong host and
network. It is using the default Compute offering.
Temporary workaround is to destroy the VR, change router.service.offering
UUID in global settings to the appropriate one and start the compute instance.
This creates the VR with appropriate compute offering. Finally reset
router.service.offering global setting.
Alternative workaround is to create the Network offering using API, not the
web interface.
<!-- Paste verbatim command output between quotes below -->
--
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]
