[jira] [Commented] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart

["Hadoop QA (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15347166#comment-15347166 ] 

Hadoop QA commented on AMBARI-17343:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12812865/AMBARI-17343.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new or modified test files.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of javac compiler warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in ambari-server.

Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/7517//testReport/
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/7517//console

This message is automatically generated.

> Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart
> --------------------------------------------------------------------------------------
>
>                 Key: AMBARI-17343
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17343
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.4.0
>            Reporter: Sandor Magyari
>            Assignee: Sandor Magyari
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17343.patch
>
>
> We created a cluster via blueprints where we did not want components to be started by Ambari (background - this was a takeover of existing cluster where services were already installed and started. We did not want STARTs to be done as they would overwrite existing configs). Towards this goal we set {{"provision_action" : "INSTALL_ONLY"}} so that when agents register with Ambari they will only do the install and not start.
> {code}
> {
>   "blueprint" : "blueprint",
>   "default_password" : "ambari",
>   "provision_action" : "INSTALL_ONLY",
>   "host_groups" : [
>      ...
>   ]
> }
> {code}
> This flag did its job as long as ambari-server was not restarted. After restart however, new agents would install and start the host-components.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)