Bug 1028443 - [GSS](6.4.z) Deployment file is removed from a wrong server group in the manage deployments screen [NEEDINFO]
Summary: [GSS](6.4.z) Deployment file is removed from a wrong server group in the mana...
Keywords:
Status: CLOSED EOL
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web Console
Version: 6.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: CR1
: EAP 6.4.5
Assignee: Harald Pehl
QA Contact: Pavel Jelinek
Russell Dickenson
URL:
Whiteboard:
Depends On: 1066151
Blocks: 1235745 1259955
TreeView+ depends on / blocked
 
Reported: 2013-11-08 13:03 UTC by Leticia Konno
Modified: 2020-12-11 11:39 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:48:23 UTC
Type: Bug
Embargoed:
msimoes: needinfo?


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker HAL-343 0 Major Resolved Deployment file is removed from a wrong server group in the manage deployments screen 2019-04-02 14:12:19 UTC

Description Leticia Konno 2013-11-08 13:03:57 UTC
Description of problem:

The error is intermittent. Needs to navigate between the content repository and server group screen.
Sometimes, a wrong server groups is selected in the manage deployment -> content repository -> server groups screen.

Version-Release number of selected component (if applicable):
JBoss EAP 6.1.1

How reproducible:

Steps to Reproduce:
1. Go to Runtime -> Manage Deployments -> Content Repository -> Server Groups
2. Select a server group
3. Select a deployment file to be removed 
4. another server groups is showed in the pop up screen

(the error is intermittent. to reproduce the issue, it is necessary to go to content repository e server groups screen several times)

Actual results:
the pop up screen for remove confirmation shows other server group from the server group selected.

Expected results:
always remove the deployment file from the server group selected. 

Additional info:
the error is intermittent, however, in a test of 10 minutes, I could reproduce the issue two times.

Comment 3 JBoss JIRA Server 2014-01-24 13:39:13 UTC
Harald Pehl <hpehl> updated the status of jira HAL-343 to Resolved

Comment 4 Harald Pehl 2014-01-24 14:07:47 UTC
Could not reproduce using HAL 2.1.0.Final

Comment 6 Harald Pehl 2014-01-26 19:49:36 UTC
Yes HAL 2.1.x will be shipped with EAP 6.3

Comment 8 Swapnil Chaudhari 2015-09-18 12:49:20 UTC
One of my customer is facing the issue in EAP 6.4.3. I am also able to reproduce the issue in EAP 6.4.3, below are the steps to reproduce :

 - I have deployed/assigned the application to tree server-groups.

 - Open the “SERVER GROUPS” tab under the “Deployments” section there is a text “Deployments assigned to this server group.” on this site.

 - After a few seconds the text changed to :
“Deployments assigned to this server group (Reference server:server-group-name)”.

 - If I click the “Remove” button before the text changed, I will get the wrong server group.

 - If I wait until the text changed, it will work as expected. 

I don’t know what happens in the background until the text changed.

Comment 9 JBoss JIRA Server 2015-09-18 17:10:46 UTC
Harald Pehl <hpehl> updated the status of jira HAL-343 to Reopened

Comment 10 Harald Pehl 2015-09-21 09:07:39 UTC
When selecting a server group in the deployment screen, the console tries to get a so called "reference server". That is a running server of the selected server group. This server is used to read the runtime information of the deployment (web context, datasources, ...)

In big domains getting the reference server might take some time. During this phase the state of the UI is not properly initialized and thus pressing the buttons might cause errors. 

The workaround is to wait until the console has found a reference server. If this is a valid workaround, I'd like to close this issue. 

Please note that the deployment screens have been thoroughly revised for EAP 7 so that this error should no longer occur.

Comment 12 Swapnil Chaudhari 2015-09-23 14:32:50 UTC
I have informed to the customer about the workaround and customer shared below thoughts :

"Is it possible to activate the buttons not until the reference server was found?
I think the management console should prevent this case. You could remove the wrong application if you don’t notice the error in the confirmation screen".

Comment 13 JBoss JIRA Server 2015-09-28 08:36:45 UTC
Harald Pehl <hpehl> updated the status of jira HAL-343 to Resolved

Comment 14 Harald Pehl 2015-09-28 08:38:00 UTC
Fixed in upstream: https://github.com/hal/core/commit/a41447875b6ee1ba6e7a7088945e7cd562ec88dc

Can be included in next CP.

Comment 18 Carlo de Wolf 2015-10-26 14:14:47 UTC
Fixed on 2.5.x: https://github.com/hal/core/commit/a41447875b6ee1ba6e7a7088945e7cd562ec88dc

Comment 19 Pavel Jelinek 2015-11-02 15:34:23 UTC
Verified for EAP 6.4.5.CP.CR1.

Comment 20 Petr Penicka 2017-01-17 11:39:55 UTC
Retroactively bulk-closing issues from released EAP 6.4 cumulative patches.

Comment 21 Marco Simões 2017-10-27 19:53:49 UTC
I have a customer facing this issue at EAP 6.4.16, and I can reproduce in CP17 too.

For reproduce this issue follow these steps:

 1- In a fresh JBoss installation, configure 4 server-groups in the domain.xml file with the below names:

    -group-1
    -group-2
    -group-3
    -group-4

 2- In the host.xml file, configure only 2 servers, like below:

   -server01 - associated to group-2 and auto-start="true"
   -server02 - associated to group-3 and auto-start="false"

 3- Start domain with that command: $JBOSS_HOME/bin/domain.sh --host-config=host.xml 

 4- Access the management Web interface and assign one deploy to all server-groups

 5- Access the deployment table and after the tab server-group, and select the group-1 and trying to remove the associated deploy. The pop-up will show "Remove xyz.war from group-4?" 

 6- Try to remove the deploy from group-2 and the correct group is printed.

 7- Try to remove the deploy from group-3 and the group-4 is printed.

 8- Try to remove the deploy from group-4 and the correct group is printed.

 9- Start the server02 where is associated to group-3.

 10- Now try to repeat the steps: 4, 5, 6, 7 and 8, but at this time, the step 7 printing the correct group to remove.

 My conclusion is when a server-group hasn't server associated or the server is down, the remove function tries to remove that deployment from the last group (alphabetical order).

 Someone can check if is this the same bug?


Note You need to log in before you can comment on or make changes to this bug.