[
https://issues.apache.org/jira/browse/AMBARI-12083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14597177#comment-14597177
]
Hadoop QA commented on AMBARI-12083:
------------------------------------
{color:green}+1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12741208/AMBARI-12083.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 1 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/3235//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/3235//console
This message is automatically generated.
> Installing Repo Packages needs to be more robust to handle the actual_version
> installed when the script is killed because of a timeout
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-12083
> URL: https://issues.apache.org/jira/browse/AMBARI-12083
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.1.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-12083.branch-2.1.patch, AMBARI-12083.patch
>
>
> When installing bits of a new repo to perform an RU, if the repo version does
> not contain a build number, then the actual_version has to be calculated.
> The problem is that this information can only be retrieved by calculating the
> delta of the versions when calling "hdp-select versions", so the only the
> first time will return a value. If the script is killed, then the
> actual_version will never be calculated and returned to the server.
> For this reason, the package installer must tolerate receiving a SIGINT or
> SIGTERM, and calculate the actual_version. Further, it helps to store it in a
> file, in case that the response or something upstream results in another
> failure.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
