You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Yusaku Sako (JIRA)" <ji...@apache.org> on 2013/11/26 03:47:35 UTC

[jira] [Commented] (AMBARI-3881) UI incorrect behavior during upgrade

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

Yusaku Sako commented on AMBARI-3881:
-------------------------------------

+1 for the patch.

> UI incorrect behavior during upgrade
> ------------------------------------
>
>                 Key: AMBARI-3881
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3881
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.4.2
>            Reporter: Jaimin D Jetly
>            Assignee: Jaimin D Jetly
>             Fix For: 1.4.2
>
>         Attachments: AMBARI-3881.patch, Upgrade.png
>
>
> This issue was discovered while upgrading the cluster to hash 87adc8c2d29b20a30f01e54c12f67dcbbe34b32e of 1.4.2 branch. The logic inside configuration_controller.js function getConfigsByTags(tagObject) has a reference to undefined variable and js error was encountered. This happened when any of the service page was rendered and program flow from quick_view_link_view.js function didInsertElement() -> setQuickLinks() -> loadTags() -> loadTagsSuccess(data) -> getSecurityProperties() -> configurationController.getConfigsByTags(tag)



--
This message was sent by Atlassian JIRA
(v6.1#6144)