[
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 anything, and the
tag remains un-updated.
* 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:
*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 anything, and the
tag remains un-updated.
* 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 anything, and
> the tag remains un-updated.
> * 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)
