ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Zang (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-17266) StackDeploys: Suse: after enabling ranger plugin save button is always present
Date Thu, 16 Jun 2016 20:37:05 GMT

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

Richard Zang updated AMBARI-17266:
----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Committed to trunk and 2.4 fcb7e7d134fccfce693c51d629df760b14034fa1

> StackDeploys: Suse: after enabling ranger plugin save button is always present
> ------------------------------------------------------------------------------
>
>                 Key: AMBARI-17266
>                 URL: https://issues.apache.org/jira/browse/AMBARI-17266
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.4.0
>            Reporter: Richard Zang
>            Assignee: Richard Zang
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-17266.patch
>
>
> 1. Deploy cluster using BP
> 2. enable ranger plugins
> 3. save configs
> Expected: Configs should be saved and save button should be disabled
> Actual: even after save and clicking Ok on confirmation "Save" button is enabled.



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

Mime
View raw message