You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Sangeeta Ravindran (JIRA)" <ji...@apache.org> on 2016/01/20 08:47:39 UTC
[jira] [Assigned] (AMBARI-13514) Service deploy wizard is not
always restored to the correct state If browser session is lost while
deploy is running
[ https://issues.apache.org/jira/browse/AMBARI-13514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sangeeta Ravindran reassigned AMBARI-13514:
-------------------------------------------
Assignee: Sangeeta Ravindran
> Service deploy wizard is not always restored to the correct state If browser session is lost while deploy is running
> --------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-13514
> URL: https://issues.apache.org/jira/browse/AMBARI-13514
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Sangeeta Ravindran
> Assignee: Sangeeta Ravindran
>
> Reproduction Steps:
> 1.Select one or more services and click on "Deploy" button. While deploy is running, kill the browser.
> 2. Restart web browser and login to ambari-server. The UI will go back to the service deploy wizard review page.
> 3. Click on "Deploy" again and you will get an error indicating that you are trying to add a service that is already installed.
> for e.g.
> org.apache.ambari.server.controller.spi.ResourceAlreadyExistsException: Attempted to create a host_component which already exists: [clusterName=hdpcluster, hostName=myhost.mydomain.com componentName=HDFS_CLIENT]
> This happens because the services have now either already been deployed or are in the middle of deploying.
> The only way to recover is to exit out of the wizard by clicking on the X at the right hand top edge.
> Expected results:
> Ambari should either retrieve the status of the deploy wizard to reflect the actual state of deploy, or go back to the dash board if browser session is lost.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)