Bug 1028443
Summary: | [GSS](6.4.z) Deployment file is removed from a wrong server group in the manage deployments screen | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Leticia Konno <lkonno> |
Component: | Web Console | Assignee: | Harald Pehl <hpehl> |
Status: | CLOSED EOL | QA Contact: | Pavel Jelinek <pjelinek> |
Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> |
Priority: | unspecified | ||
Version: | 6.1.1 | CC: | bbaranow, bmaxwell, brian.stansberry, cdewolf, hpehl, jawilson, jkudrnac, jmartisk, pjelinek, schaudha, vtunka, wfink |
Target Milestone: | CR1 | Keywords: | Reopened |
Target Release: | EAP 6.4.5 | Flags: | msimoes:
needinfo?
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-19 12:48:23 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1066151 | ||
Bug Blocks: | 1235745, 1259955 |
Description
Leticia Konno
2013-11-08 13:03:57 UTC
Harald Pehl <hpehl> updated the status of jira HAL-343 to Resolved Could not reproduce using HAL 2.1.0.Final Yes HAL 2.1.x will be shipped with EAP 6.3 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. Harald Pehl <hpehl> updated the status of jira HAL-343 to Reopened 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. 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". Harald Pehl <hpehl> updated the status of jira HAL-343 to Resolved Fixed in upstream: https://github.com/hal/core/commit/a41447875b6ee1ba6e7a7088945e7cd562ec88dc Can be included in next CP. Verified for EAP 6.4.5.CP.CR1. Retroactively bulk-closing issues from released EAP 6.4 cumulative patches. 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? |