Bug 1319994
| Summary: | [GSS](6.4.z) Patch Management doesn't show the "Latest Applied Patch" correctly. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | xuzhan | ||||
| Component: | Web Console | Assignee: | Enrique Gonzalez Martinez <egonzale> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Pavel Jelinek <pjelinek> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.4.0 | CC: | bbaranow, bmaxwell, brian.stansberry, egonzale, hbraun, hpehl, jason.greene, jawilson, jdoyle, jkudrnac, jtruhlar, kconner, mcada, msimka, olubyans, pjelinek | ||||
| Target Milestone: | CR1 | ||||||
| Target Release: | EAP 6.4.8 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-01-17 12:35:15 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: | |||||||
| Bug Blocks: | 1279553, 1306860 | ||||||
| Attachments: |
|
||||||
Could you please post the CLI commands you used? Thanks. Yes, the commands are: ~~~ patch apply --host=s1 /tmp/patches/eap6.4.x/jboss-eap-6.4.1-patch.zip shutdown --restart=true --host=s1 patch apply --host=master /tmp/patches/eap6.4.x/jboss-eap-6.4.1-patch.zip shutdown --restart=true --host=master patch apply --host=master /tmp/patches/eap6.4.x/jboss-eap-6.4.2-patch.zip shutdown --restart=true --host=master patch apply --host=s1 /tmp/patches/eap6.4.x/jboss-eap-6.4.2-patch.zip shutdown --restart=true --host=s1 patch apply --host=master /tmp/patches/eap6.4.x/jboss-eap-6.4.4-patch.zip shutdown --restart=true --host=master patch apply --host=s1 /tmp/patches/eap6.4.x/jboss-eap-6.4.5-patch.zip shutdown --restart=true --host=s1 patch apply --host=master /tmp/patches/eap6.4.x/jboss-eap-6.4.5-patch.zip shutdown --restart=true --host=master patch apply --host=s1 /tmp/patches/eap6.4.x/jboss-eap-6.4.6-patch.zip shutdown --restart=true --host=s1 patch apply --host=master /tmp/patches/eap6.4.x/jboss-eap-6.4.6-patch.zip shutdown --restart=true --host=master ~~~ this is not related to the patch, but related to the web console. https://github.com/hal/core/blob/2.5.12.Final/gui/src/main/java/org/jboss/as/console/client/shared/patching/PatchManager.java#L225 this line relies on the (which is wrong) https://github.com/hal/core/blob/2.5.12.Final/gui/src/main/java/org/jboss/as/console/client/shared/patching/PatchManager.java#L52. PR sent 2.5.x (6.4.z stream) https://github.com/hal/core/pull/186 Harald Pehl <hpehl> updated the status of jira HAL-1072 to Resolved PR merged Verified with EAP 6.4.8.CP.CR2 Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4051 to Reopened Carlo de Wolf <cdewolf> updated the status of jira JBEAP-4051 to Resolved Pavel Jelinek <pjelinek> updated the status of jira JBEAP-4051 to Reopened Jiri Pallich <jpallich> updated the status of jira JBEAP-4051 to Closed Retroactively bulk-closing issues from released EAP 6.4 cumulative patches. |
Created attachment 1138873 [details] screen shot of issue 1-5 Description of problem: In EAP 6.4.0, after patching 6.4.6 on slave host and restart it successfully. Patch Management shows the "Latest Applied Patch" is "jboss-eap-6.4.5.CP", although the "jboss-eap-6.4.6.CP" was list in "Recent Patch History" below. After patching on Master host and restart it successfully, the "Latest Applied Patch" of slave host is "n/a". Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. unzip eap 6.4.0 on two machines respectively,setup a domain(one is DC the other is HC). 2. enter in CLI console, start to patch DC and HC 3. patch 6.4.1 on HC then restart it.(issue 1) 4. patch 6.4.1 on DC then restart it. 5. patch 6.4.2 on DC then restart it.(issue 2) 6. patch 6.4.2 on HC then restart it. 7. patch 6.4.4 on DC then restart it.(issue 3) 8. patch 6.4.5 on HC then restart it.(issue 4) 9. patch 6.4.5 on DC then restart it. 10.patch 6.4.6 on HC then restart it.(issue 5) 11.patch 6.4.6 on DC then restart it. Please refer to screen shot of issues 1-5 Actual results: During the whole process, "Patch Management" shows incorrect messages from issue 1-5. Expected results: Additional info: Please let us know if it is a bug or not, can we safely ignore it?