Bug 1263742
| Summary: | Subsequent update (JON 3.3.0 -> CP1 -> CP2 -> Cn) and direct update (JON 3.3.0 -> CPn) produce different content of JON directory | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Filip Brychta <fbrychta> | ||||||||
| Component: | Launch Scripts, Productization | Assignee: | Simeon Pinder <spinder> | ||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Filip Brychta <fbrychta> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | JON 3.3.4 | Keywords: | Triaged | ||||||||
| Target Milestone: | ER01 | ||||||||||
| Target Release: | JON 3.3.4 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2015-10-29 15:53:34 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: | |||||||||||
| Attachments: |
|
||||||||||
Created attachment 1074068 [details]
files visible only on server1 - agent dir
Created attachment 1074405 [details]
files visible only on server1
This is fixed with commit: 1c4ea168a800bc5a to jon.git. While there are quite a bit of additional files that were not included, the bulk of them were with jbossas/* which fully uses modules and the presence of extra files is not an issue for, because the exact version to use(even with extra copies around) is specified in the module.xml file. This is to say that most of these were harmless, but by adding these files also to the removed list should bring parity to CP1>CP2>CPN vs. GA>CPN. @QE, this exercise should be done every time we do a significant JON rebase in the future. The JON cumulative patch process was not designed to handle rebases of the EAP container during the patch creation process and as such misses these subtle changes. The remainder are from CVE fixes. Moving to ON_QA as available to test with the following build: https://brewweb.devel.redhat.com/buildinfo?buildID=460382 *Note: jon-server-patch-3.3.0.GA.zip maps to ER01 build of jon-server-3.3.0.GA-update-04.zip. Verified on Version : 3.3.0.GA Update 04 Build Number : 821a526:fa7b1a1 Ignore previous comment it's not correct. Original issue is fixed now only following files: /home/hudson/jon-server-3.3.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-serverplugins/fabric-groups-plugin-7.3.1.redhat-379.jar 57829eeec13bdb02ce08bc58b0e34ff5 /home/hudson/jon-server-3.3.0.GA/modules/org/rhq/server-startup/main/deployments/rhq.ear/rhq-serverplugins/rhq-serverplugin-wfly-patch-bundle-4.12.0.JON330GA.jar eea052728a19c6c8b6c6311305b1c51a are visible only on server2. |
Created attachment 1074067 [details] files visible only on server1 Description of problem: $Summary Version-Release number of selected component (if applicable): JON 3.3.4.DR1 How reproducible: Always Steps to Reproduce: 1. on server1: a) install JON 3.3.0.GA b) apply CP1 c) apply CP2...CP4 2. on server2: a) install JON 3.3.0.GA b) apply CP4 3. compare content of jon-server-3.3.0.GA from server1 and server2 4. compare content of rhq-agent from server1 and server2 Actual results: There is lot of files which are on server1 only not being visible on server2. e.g. server1 contains 2 versions of jboss-remote-naming (jboss-remote-naming-1.0.9.Final-redhat-1.jar and jboss-remote-naming-1.0.11.Final-redhat-1.jar) but server2 contains only one version. See attached list. Expected results: Content of directories from server1 and server2 should match (except for expected differences like logs, config files...) Additional info: Majority of files is from jbossas/modules, one is from modules/org/rhq/server-startup/