You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Antonenko Alexander (JIRA)" <ji...@apache.org> on 2014/07/30 18:54:38 UTC

[jira] [Commented] (AMBARI-6680) On CentOS 5, BG Operation window isn't shown after stop all services

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

Antonenko Alexander commented on AMBARI-6680:
---------------------------------------------

+1 for the patch

> On CentOS 5, BG Operation window isn't shown after stop all services
> --------------------------------------------------------------------
>
>                 Key: AMBARI-6680
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6680
>             Project: Ambari
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 1.6.1
>         Environment: ambari-server version: ambari-server-1.6.1-87
> ambari-server --hash: aa698147fba78af8c5e1d479dea4783bbfd82278
> HDP Stack: 2.1
> Ambari DB: :PostgreSQL
> Security:no
> HA: no
> OS: CentOS 5
>            Reporter: Oleg Nechiporenko
>            Assignee: Oleg Nechiporenko
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: AMBARI-6680.patch
>
>
> *STR*
> # Deploy Ambari with HDP on Centos 5
> # Upgrade to according to http://dev.hortonworks.com.s3.amazonaws.com/HDPDocuments/Ambari-Trunk/bk_upgrading_Ambari/content/ambari-chap7_2x.html
> # Login to UI and stop all services
> *Actual result*
> JS errors:
> {code}
> "NetworkError: 404 Not Found - http://c5901.ambari.apache.org:8080/api/v1/persist/admin-settings-show-bg-admin?_=1404903578649"
> admin-...3578649
> "NetworkError: 404 Not Found - http://c5901.ambari.apache.org:8080/api/v1/persist/hostPopup-pagination-displayLength-admin?_=1404903581980"
> hostPo...3581980
> {code}
> Bg operation window haven't appeared
> *Expeted result*
> Bg operation window should appear
> This reproduces only first time after upgrade, all sequential operations are performed as expected. This is an issue mainly for upgrade autotests. See also attached video with reproduce 



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