Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Tue, 16 Dec 2014 19:48:14 +0000 (UTC)
From: "Jordan Pilat (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12762085.1418759249000.36687.1418759294913@Atlassian.JIRA>
In-Reply-To: <JIRA.12762085.1418759249000@Atlassian.JIRA>
References: <JIRA.12762085.1418759249000@Atlassian.JIRA>
 <JIRA.12762085.1418759249262@arcas>
Subject: [jira] [Updated] (AMBARI-8739) Submitting an unchanged
 configuration via the API incorrectly prompts for a restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jordan Pilat updated AMBARI-8739:
---------------------------------
    Description: 
*Steps to Reproduce*
# Submit a given configuration to Ambari via the API, with a given tag and set of properties*.
# Restart components as required.
# Submit the same configuration as in *Step 1*, only with a new tag.
# Observe the status of the component via the Ambari web application.

*Expected Result*
As the properties remain unchanged, none have been added, and none have been removed, a restart of the component is not actually required.

The server should not update the tag, and should respond to the second API request with a rejection message, noting that the configuration is unchanged.  A restart would not be required.
This would match the behavior seen in the web application, when one opens the "Configs" tab and presses "Save" without actually changing everything, including the tag.

Alternately, the actual configuration could simply be updated with the new tag from *Step 3*.  A restart would not be required.

*Actual Result*
The components for which you submitted the configurations must be restarted again after receiving the same configuration a second time.


* - Using the option to both create and apply a configuration in one call, as seen [HERE|https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md].

  was:
*Issue Description*

*Steps to Reproduce*
# Submit a given configuration to Ambari via the API, with a given tag and set of properties*.
# Restart components as required.
# Submit the same configuration as in *Step 1*, only with a new tag.
# Observe the status of the component via the Ambari web application.

*Expected Result*
As the properties remain unchanged, none have been added, and none have been removed, a restart of the component is not actually required.

The server should not update the tag, and should respond to the second API request with a rejection message, noting that the configuration is unchanged.  A restart would not be required.
This would match the behavior seen in the web application, when one opens the "Configs" tab and presses "Save" without actually changing everything, including the tag.

Alternately, the actual configuration could simply be updated with the new tag from *Step 3*.  A restart would not be required.

*Actual Result*
The components for which you submitted the configurations must be restarted again after receiving the same configuration a second time.


* - Using the option to both create and apply a configuration in one call, as seen [HERE|https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md].


> Submitting an unchanged configuration via the API incorrectly prompts for a restart
> -----------------------------------------------------------------------------------
>
>                 Key: AMBARI-8739
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8739
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 1.5.1
>         Environment: Hortonworks Sandbox v2.1
>            Reporter: Jordan Pilat
>              Labels: API, APIBug
>
> *Steps to Reproduce*
> # Submit a given configuration to Ambari via the API, with a given tag and set of properties*.
> # Restart components as required.
> # Submit the same configuration as in *Step 1*, only with a new tag.
> # Observe the status of the component via the Ambari web application.
> *Expected Result*
> As the properties remain unchanged, none have been added, and none have been removed, a restart of the component is not actually required.
> The server should not update the tag, and should respond to the second API request with a rejection message, noting that the configuration is unchanged.  A restart would not be required.
> This would match the behavior seen in the web application, when one opens the "Configs" tab and presses "Save" without actually changing everything, including the tag.
> Alternately, the actual configuration could simply be updated with the new tag from *Step 3*.  A restart would not be required.
> *Actual Result*
> The components for which you submitted the configurations must be restarted again after receiving the same configuration a second time.
> * - Using the option to both create and apply a configuration in one call, as seen [HERE|https://github.com/apache/ambari/blob/trunk/ambari-server/docs/api/v1/configuration.md].


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