Bug 1072624 - Replace deployment in admin console ignores runtime-name
Summary: Replace deployment in admin console ignores runtime-name
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.2.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: DR0
: EAP 6.4.0
Assignee: Harald Pehl
QA Contact: Pavel Jelinek
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-04 22:31 UTC by dereed
Modified: 2019-08-19 12:45 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-452 0 Major Resolved Replace deployment in admin console ignores runtime-name 2015-08-19 13:38:47 UTC

Description dereed 2014-03-04 22:31:04 UTC 
Description of problem:
When using the "Replace" deployment feature in the admin console, the entered Runtime Name is ignored.

Version-Release number of selected component (if applicable):
6.2 CP1

How reproducible:
Always.

Steps to Reproduce:
1. Go to "Manage Deployments" screen in the admin console
2. Choose a deployment and click "Replace" button
3. Choose a new file and click "Next".
4. Enter a Runtime Name and click "Save".

Actual results:
The Runtime Name is set to the same value as Name, not the entered Runtime Name.

Expected results:
The Runtime Name is set to the value specified.

Additional info:
Comment 1 dereed 2014-03-04 22:32:18 UTC 
Workarounds:
- remove and then add again in the GUI
- do the replace with the CLI:

    deploy /path/to/myapp-1.2.3.ear --name="myapp" --runtime-name="myapp.ear" --force
Comment 2 JBoss JIRA Server 2014-07-10 11:51:48 UTC 
Harald Pehl <hpehl> updated the status of jira HAL-452 to Coding In Progress
Comment 3 JBoss JIRA Server 2014-07-10 12:06:15 UTC 
Harald Pehl <hpehl> updated the status of jira HAL-452 to Resolved
Comment 4 Pavel Jelinek 2014-11-26 09:30:48 UTC 
Should this still remain in POST state?
Comment 5 Pavel Jelinek 2014-12-05 13:19:39 UTC 
Verified for EAP 6.4.0.DR12
Note You need to log in before you can comment on or make changes to this bug.