Bug 1126053
| Summary: | content deployment version history is overridden after update | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Armine Hovsepyan <ahovsepy> | ||||||||||
| Component: | Content | Assignee: | RHQ Project Maintainer <rhq-maint> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Mike Foley <mfoley> | ||||||||||
| Severity: | high | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | JON 3.3.0 | CC: | ahovsepy, mfoley, myarboro, snegrea | ||||||||||
| Target Milestone: | ER03 | ||||||||||||
| Target Release: | JON 3.3.0 | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2014-09-05 14:14:08 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 923382 [details]
deploy-new-version
Created attachment 923383 [details]
version-after-update
By repeating steps 8 through 10 without changing the content you are basically reinstalling the same content over and over again. The version history keeps track of actual content deployed, which is the same in your case (even though you specified a different version at install time). The content system computes a hash for the entire content of a package. This hash is the actual version of the package. The version displayed in the UI is just a display version. If users upload the same content but with different file name, the content system will just identify it as the same package and will update the name to the latest. What you are seeing is a known limitation of the content system due to the move to strong hash versioning of packages. A correct teste case would be to repeat the steps above but with different packages each time. For example, add a picture or a text file to the archive each time. The history should reflect that different packages were installed and the different packages will be all listed in the history. Created attachment 936221 [details]
deploy-content-history
|
Created attachment 923381 [details] before-update-history Description of problem: content deployment version history is overridden after update Version-Release number of selected component (if applicable): jon 3.3 DR1 How reproducible: always Steps to Reproduce: 1. Start JBoss EAP 6.1 standalone server. 2. Start JBoss ON 3.2 system. 3. Import JBoss EAP server into inventory. 4. Configure connection settings for newly imported resource. 5. Deploy jboss-as-helloworld.war to JBoss EAP server. 6. Navigate to the content page of the jboss-as-helloworld.war resource. 7. Select the new tab. 8. Upload a new version of helloworld.war 9. Install uploaded war 10. Navigate to history 11. repeate steps 8-11 Actual results: content deployment version history is overridden after update Expected results: content deployment version history is NOT overridden after update, history of all versions is kept Additional info: screen-shots attached