ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-14987) assign_master_component.js does not show recommendations while adding master component for a service which is already installed
Date Fri, 26 Feb 2016 03:27:18 GMT

    [ https://issues.apache.org/jira/browse/AMBARI-14987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15168365#comment-15168365
] 

Hudson commented on AMBARI-14987:
---------------------------------

FAILURE: Integrated in Ambari-branch-2.2 #420 (See [https://builds.apache.org/job/Ambari-branch-2.2/420/])
AMBARI-14987: assign_master_component.js does not show recommendations (jaoki: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=b0a7149373d48e2c7b4cce06b0b26a6d1c87b0ec])
* ambari-web/test/mixins/wizard/assign_master_components_test.js
* ambari-web/app/mixins/wizard/assign_master_components.js


> assign_master_component.js does not show recommendations while adding master component
for a service which is already installed
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-14987
>                 URL: https://issues.apache.org/jira/browse/AMBARI-14987
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>            Reporter: Matt
>            Assignee: Matt
>            Priority: Minor
>             Fix For: trunk, 2.2.2
>
>         Attachments: AMBARI-14987-branch-2.2-feedback-orig.patch, AMBARI-14987-branch-2.2-v1.patch,
AMBARI-14987-branch-2.2-v2.patch, AMBARI-14987-branch-2.2.patch, AMBARI-14987-trunk-feedback-orig.patch,
AMBARI-14987-trunk-v1.patch, AMBARI-14987-trunk-v2.patch, AMBARI-14987-trunk-v3.patch, AMBARI-14987-trunk.patch
>
>
> On the assign masters page for the wizard, recommendations are not shown for a master
component that is being added for an installed service.
> This happens while adding HAWQSTANDBY to the cluster using the 'Add HAWQSTANDBY' wizard
(situation: HAWQ service is already installed on the cluster). 
> The fix might also solve the issue where there is a installed service and the upgrade
of the service includes installing a new master component



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

Mime
View raw message