[
https://issues.apache.org/jira/browse/AMBARI-10136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14370523#comment-14370523
]
Hudson commented on AMBARI-10136:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #2081 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/2081/])
AMBARI-10136. Web Client Continues To Make Requests After Logout
(alexantonenko) (hiveww:
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=dc6540318d14f8d8ead089de5707374d4d744b35)
* ambari-web/app/controllers/wizard/step9_controller.js
> Web Client Continues To Make Requests After Logout
> --------------------------------------------------
>
> Key: AMBARI-10136
> URL: https://issues.apache.org/jira/browse/AMBARI-10136
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Fix For: 2.1.0
>
> Attachments: AMBARI-10136.patch
>
>
> During the provisioning of a new cluster, the web client continues to make
> requests after logging out.
> Reproduction Steps:
> 1) Create a new cluster
> 2) Deploy the cluster and watch the progress bars start
> 3) While the cluster is still being deployed, log out.
> 4) Observe that after the logout URL is invoked, there are still requests
> being made to api/v1/clusters/c1/requests/
> Attaching a HAR file that shows the requests to api/v1/clusters/c1/requests/
> followed by a request to api/v1/logout, followed by more requests to
> api/v1/clusters/c1/requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
