Description of problem:
When user tries to deploy the newer version of existing archive with the same runtime name, deployment fails with message: "Deployment {} already exists on this server."
But is should give the user the option to proceed or cancel the deployment.
Version-Release number of selected component (if applicable):
DR2
How reproducible:
always
Steps to Reproduce:
1. Go to Middleware Server.
2. Deploy some archive, give a runtime name while deploying.
3. Make sure deployment is successful and visible.
4. Select another archive to upload but giving the same runtime name as in step2.
It will fail to deploy.
Actual results:
Deployment fails with message "Deployment {} already exists on this server."
Expected results:
According to the new requirements in "OPR-032a", it should give the user the option to Proceed or Cancel the deployment.
Description of problem: When user tries to deploy the newer version of existing archive with the same runtime name, deployment fails with message: "Deployment {} already exists on this server." But is should give the user the option to proceed or cancel the deployment. Version-Release number of selected component (if applicable): DR2 How reproducible: always Steps to Reproduce: 1. Go to Middleware Server. 2. Deploy some archive, give a runtime name while deploying. 3. Make sure deployment is successful and visible. 4. Select another archive to upload but giving the same runtime name as in step2. It will fail to deploy. Actual results: Deployment fails with message "Deployment {} already exists on this server." Expected results: According to the new requirements in "OPR-032a", it should give the user the option to Proceed or Cancel the deployment.