ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandor Magyari (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17343) Blueprint attribute provision_action=INSTALL_ONLY loses its value after server restart
Date Tue, 28 Jun 2016 09:41:57 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-17343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sandor Magyari updated AMBARI-17343:
------------------------------------
    Attachment: AMBARI-17343_v2.patch

> 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_v2.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)

Mime
View raw message