[
https://issues.apache.org/jira/browse/AMBARI-14621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095152#comment-15095152
]
Hadoop QA commented on AMBARI-14621:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12781909/AMBARI-14621-3.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/4888//console
This message is automatically generated.
> Blueprint deploy should update the value localhost for HAWQMASTER and
> HAWQSTANDBY
> ---------------------------------------------------------------------------------
>
> Key: AMBARI-14621
> URL: https://issues.apache.org/jira/browse/AMBARI-14621
> Project: Ambari
> Issue Type: Bug
> Components: blueprints
> Affects Versions: 2.2.1
> Reporter: bhuvnesh chaudhary
> Assignee: bhuvnesh chaudhary
> Fix For: trunk, 2.2.0
>
> Attachments: AMBARI-14621-3.patch
>
>
> Blueprint deploy should update the value localhost for HAWQMASTER,
> HAWQSTANDBY with the name of their respective component hostname. It should
> also update the value of hawq_dfs_url to NAMENODE HOST.
> The logic to replace the hostname is currently only on the Web UI due to
> which during deploy, hawq_master_address_host, hawq_standby_address_host and
> hawq_dfs_url are set to localhost and hawq start fails.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
