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

Szilard Antal updated AMBARI-25418:
-----------------------------------
    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

> Cannot select any configuration in logsearch configuration editor
> -----------------------------------------------------------------
>
>                 Key: AMBARI-25418
>                 URL: https://issues.apache.org/jira/browse/AMBARI-25418
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 2.7.4, 2.7.5
>            Reporter: Szilard Antal
>            Assignee: Szilard Antal
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 2.7.5
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> In the logsearch configuration editor it is not possible add or select 
> another configuration. It is also not possible to navigate back the service 
> log page.
> The following error appears in the dev console.
> {code:java}
> ERROR Error: Uncaught (in promise): TypeError: e.find is not a function
> TypeError: e.find is not a function
> at main.bundle.js:1
> at Array.forEach (<anonymous>)
> at t.set as selection (main.bundle.js:1)
> at t.writeValue (main.bundle.js:1)
> at t._next (main.bundle.js:1)
> at t.__tryOrSetError (vendor.bundle.js:999)
> at t.next (vendor.bundle.js:999)
> at t._next (vendor.bundle.js:999)
> at t.next (vendor.bundle.js:999)
> at t._emitFinal (vendor.bundle.js:999)
> at l (polyfills.bundle.js:43)
> at polyfills.bundle.js:43
> at e.invokeTask (polyfills.bundle.js:36)
> at Object.onInvokeTask (vendor.bundle.js:443)
> at e.invokeTask (polyfills.bundle.js:36)
> at t.runTask (polyfills.bundle.js:36)
> at r (polyfills.bundle.js:36)
> at o.invokeTask as invoke (polyfills.bundle.js:36)
> at j (polyfills.bundle.js:8)
> at XMLHttpRequest._ (polyfills.bundle.js:8){code}
> Occasionally, after refreshing the page the error didn’t appear and 
> everything worked fine.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to