[
https://issues.apache.org/jira/browse/AMBARI-22073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16183980#comment-16183980
]
Hadoop QA commented on AMBARI-22073:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12889290/AMBARI-22073.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 4 new
or modified test files.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in
ambari-web.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/12366//console
This message is automatically generated.
> UI:VersionTag is no more needed for config creation/update
> ----------------------------------------------------------
>
> Key: AMBARI-22073
> URL: https://issues.apache.org/jira/browse/AMBARI-22073
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 3.0.0
> Reporter: Andrii Tkach
> Assignee: Andrii Tkach
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: AMBARI-22073.patch
>
>
> As of now, if versionTag is not set in API request we will generate it on BE
> automatically. So, no more need to generate and add it to request.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
