[
https://issues.apache.org/jira/browse/BROOKLYN-547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16240616#comment-16240616
]
ASF GitHub Bot commented on BROOKLYN-547:
-----------------------------------------
GitHub user aledsage opened a pull request:
https://github.com/apache/brooklyn-server/pull/881
BROOKLYN-547: fix VanillaSoftwareProcess.restart with no ssh-monitoring
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/aledsage/brooklyn-server BROOKLYN-547
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/brooklyn-server/pull/881.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 #881
----
commit b8782c253f87f79d84c65c93f0391ec527729383
Author: Aled Sage <[email protected]>
Date: 2017-11-06T17:54:28Z
BROOKLYN-547: fix VanillaSoftwareProcess.restart with no ssh-monitoring
----
> VanillaSoftwareProcess.restart fails if sshMonitoring disabled
> --------------------------------------------------------------
>
> Key: BROOKLYN-547
> URL: https://issues.apache.org/jira/browse/BROOKLYN-547
> Project: Brooklyn
> Issue Type: Bug
> Reporter: Aled Sage
>
> When using {{VanillaSoftwareProcess}} with {{sshMonitoring.enabled: false}},
> the entity is set on fire if you call the {{restart}} effector.
> This is because... when the entity transitions to service.isUp=false during
> the restart, it triggers the enricher
> {{UpdatingNotUpFromServiceProcessIsRunning}}, which populates the
> service-not-up-indicator with {{service.process.isRunning}}. This is never
> cleared because we are not polling over ssh for the check-running.
> A solution would be to remove this enricher in {{VanillaSoftwareProcess}}, if
> ssh-monitoring is disabled.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
