[
https://issues.apache.org/jira/browse/AIRAVATA-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eroma updated AIRAVATA-2286:
----------------------------
Description:
Steps taken:
1. Application has two deployments.
2. We delete deployment 1
3. Clone an experiment which used deployment 1
4. In 'Edit experiment' of cloned experiment now shows only the existing
deployment but the queue details are from the previously deleted deployment.
5. When the experiment is launched it fails in the backend but stays in CREATED
in the UI.
6. It fails if the queue names are different from one deployment to the other.
7. Ideally the queue details also should get updated as per the new deployment
details.
was:
Steps taken:
1. Application has two deployments.
2. We delete deployment 1
3. Clone an experiment which used deployment 1
4. In 'Edit experiment' of cloned experiment now shows only the existing
deployment but the queue details are from the previously deleted deployment.
5. When the experiment is launched it fails in the backend but stays in CREATED
in the UI.
6. It fails if the queue names are different from one deployment to the other.
> When a deployment is deleted, cloned experiment will still have queue details
> of the previous deployment
> --------------------------------------------------------------------------------------------------------
>
> Key: AIRAVATA-2286
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2286
> Project: Airavata
> Issue Type: Bug
> Components: PGA PHP Web Gateway
> Environment: dev.seagrid.org
> Reporter: Eroma
> Assignee: Marcus Christie
> Fix For: 0.17
>
>
> Steps taken:
> 1. Application has two deployments.
> 2. We delete deployment 1
> 3. Clone an experiment which used deployment 1
> 4. In 'Edit experiment' of cloned experiment now shows only the existing
> deployment but the queue details are from the previously deleted deployment.
> 5. When the experiment is launched it fails in the backend but stays in
> CREATED in the UI.
> 6. It fails if the queue names are different from one deployment to the other.
> 7. Ideally the queue details also should get updated as per the new
> deployment details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
