ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-7059) FE: Adding Sqoop service right after install doesnt auto-select Client
Date Thu, 28 Aug 2014 15:20:09 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-7059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Aleksandr Kovalenko updated AMBARI-7059:
----------------------------------------

    Attachment: AMBARI-7059.patch

> FE: Adding Sqoop service right after install doesnt auto-select Client
> ----------------------------------------------------------------------
>
>                 Key: AMBARI-7059
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7059
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.7.0
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-7059.patch
>
>
> Set App.supports.serverRecommendValidate=true
> When installing, deselect SQOOP service and finish install. Right after that go into
add-service wizard and add SQOOP service. The /recommendations POST call for host-layout correctly
recommends adding SQOOP component to a host. The UI however does not select that host (image
attached), resulting in an ERROR from /validations call.
> Since SQOOP is a client, the Client checkbox should be checked.
> Then, when the Client checkbox is checked, and Deploy is hit, it seems to be adding all
client components (7 PUT calls with 400-Bad Request) (image attached).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message