rajujith opened a new issue, #8284:
URL: https://github.com/apache/cloudstack/issues/8284
<!--
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
* Improvement Request
##### COMPONENT NAME
<!--
Categorize the issue, e.g. API, VR, VPN, UI, etc.
-->
~~~
VR,VMware
~~~
##### CLOUDSTACK VERSION
<!--
New line separated list of affected versions, commit ID for issues on main
branch.
-->
~~~
4.17.2
~~~
##### SUMMARY
<!-- Explain the problem/feature briefly -->
When a VR is stopped on cloudstack then management/control IP is released.
If the VR is powered on later on the hypervisor the VR will function
normally with its previous management IP but CloudStack won’t find this IP
information although the power state is synced.
This situation could result in operations issues on the guest works since
either :
There is a management IP on the VR but cloudstack doesn’t know about it
so most of the operations can fail.
The previously released IP could be allocated to a new VR resulting in
IP conflict and potentially configuring the wrong VR with network
configurations as well.
##### 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.Deploy a VM on a new isolated guest network with a default offering.
2.Stop the VR in cloudStack
3. Start the VR on the hypervisor.
~~~
--
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]
