GitHub user ProjectMoon opened a pull request:
https://github.com/apache/cloudstack/pull/1162
Add support for not (re)starting server after cloud-setup-management.
This adds an option to the cloud-setup-management script to not start
the management server after a successful configuration of it.
The primary motivation for this is to avoid circular dependency issues on
systems that use systemd. When calling cloud-setup-management from a unit with
a Before= directive on a service depending on
cloudstack-management, the process will deadlock because /usr/bin/service
will delegate to systemd, which is waiting for the Before service to start.
Executing the cloud-setup-management script with this new `--no-start`
option will simply leave the management server stopped after a successful
configuration. systemd can then be bypassed with `export
_SYSTEMCTL_SKIP_REDIRECT=1` and using the init.d script.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greenqloud/cloudstack pr-no-start
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1162.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1162
----
commit 1f2357dc22f78acc8a5e6a1cb3e9269488aa499f
Author: jeff <j...@greenqloud.com>
Date: 2015-12-03T18:36:10Z
Add support for not (re)starting server after cloud-setup-management.
This adds an option to the cloud-setup-management script to not start
the management server after a successful configuration of it. The
primary motivation for this is to avoid circular dependency issues on
systems that use systemd. When calling cloud-setup-management from a
unit with a Before= directive on a service depending on
cloudstack-management, the process will deadlock because
/usr/bin/service will delegate to systemd, which is waiting for the
Before service to start.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
