CKrieger2020 opened a new issue, #6298:
URL: https://github.com/apache/cloudstack/issues/6298
<!--
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 -->
* Other
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
UI, IP
##### CLOUDSTACK VERSION
<!--
-->
4.16.0.0
##### SUMMARY
<!-- Explain the problem/feature briefly -->
I am trying to find a method of placing newly deployed VM's on the same
network as my management server, but so far it only allows me to create guest
VM's behind a NAT with a private IP address. I need to create multiple VM's
hosting services that can be routed to an external DNS. My concern is that the
NAT will make routing to these machines impossible.
I have tried changing the network offering on my guest network from
"offering for isolated network with NAT service enabled" to "offering for
isolated network with no NAT service enabled", but it gives me this error:
"can't upgrade from network offering edad787d-baa0-4ca8-a67b-bd288adc6d37 to
052cee24-272b-44f1-a4df-4b5da7a30744; check logs for more information"
I would choose this during network deployment, but I do not have the option
to choose "offering for isolated network with no NAT service enabled" until
after deployment.
I would appreciate any advice you can give to help guide me from here as I
am new to cloudstack
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
Place all deployed VM's on same IP range as the management console itself.
##### ACTUAL RESULTS
<!-- What actually happened? -->
Forced to deploy VM's behind NAT per default configuration
<!-- 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]
