Atiqul-Islam opened a new issue, #7710:
URL: https://github.com/apache/cloudstack/issues/7710
<!--
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
~~~
Cloudstack Management Server get into a bad state after system restart.
~~~
##### CLOUDSTACK VERSION
~~~
4.17.2
~~~
##### CONFIGURATION
CloudStack with Isolated Network running CAPC
##### OS / ENVIRONMENT
<!--
Information about the environment if relevant, N/A otherwise
-->
##### SUMMARY
Restarting the bare metal machine puts cloudstack in a bad state.
Restarting the management server service seems to resolve the issue.
Is there any way to ensure that restarting the bare metal will bring up the
Management Server in the last known state before the restart.
##### STEPS TO REPRODUCE
Install CloudStack 4.17.2 on Ubuntu Server 22.04
Reboot the bare metal system
##### EXPECTED RESULTS
<!-- What did you expect to happen when running the steps above? -->
~~~
I expect CloudStack to automatically come up in the state it was when the
system was rebooted.
~~~
##### ACTUAL RESULTS
<!-- Paste verbatim command output between quotes below -->
~~~
Management Server ends up in a bad state.
Restarting the management server via the command `sudo systemctl restart
cloudstack-management-server` resolves the issue.
~~~
--
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]
