Bug 788776 - Package Version Incorrectly Updated When Package Uploaded from UI
Package Version Incorrectly Updated When Package Uploaded from UI
Product: RHQ Project
Classification: Other
Component: Core UI (Show other bugs)
Unspecified Unspecified
high Severity high (vote)
: ---
: JON 3.0.1
Assigned To: Stefan Negrea
Mike Foley
Depends On: 769986
Blocks: 788629
  Show dependency treegraph
Reported: 2012-02-08 19:05 EST by Stefan Negrea
Modified: 2013-09-03 11:15 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 769986
Last Closed: 2013-09-03 11:15:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
verification image (129.13 KB, image/png)
2012-02-15 14:27 EST, Mike Foley
no flags Details

  None (edit)
Description Stefan Negrea 2012-02-08 19:05:00 EST
+++ This bug was initially created as a clone of Bug #769986 +++

Description of problem:
The JSF UI incorrectly populates the version and display version for uploaded packages. Also, the version is a required field which forces users to type information that could be discovered later.

How reproducible:
Every time.

Steps to Reproduce:
1. Inventory a Tomcat server (or JBoss AS4 or AS5)
2. Go to the Content tab of a war resource
3. Upload a new package for the resource
4. Review rhq_package_version table entries created by the command.
5. Review the installation history for the resource.
Actual results:
In the database, version is the value entered by the user in the UI, and the display version is empty. The installation history shows incorrect versions for the installed packages.

Expected results:
In the database, the version is the SHA256 of the uploaded content, and the display version is the version entered by the user. The installation history should show the display version if not empty (if empty then default to version).

Additional info:
The version field should be optional going forward. This could be discovered and reported back by the agent. If the user actually enters one then it will be preserved, however if the user leaves this field black then the discovery process will attempt to retrieve display version from the actual manifest.

This BZ supports the overall set of enhancements required by the Content System.

--- Additional comment from mfoley@redhat.com on 2012-01-23 15:31:19 EST ---

2nd verification step for QE

UI Test (applicable to BZ 761593, 767247, 767393, 769986)

1) RHQ server started, RHQ agent running
2) Inventoried Tomcat Server, JBoss AS4 or JBoss EAP5.1
3) A sample war application to be deployed to the application server

1) Navigate in the UI to the selected application resource, content tab, history subtab.
2) Navigate to the New subtab.
3) Upload a new war package for the resource. Follow the guided UI but do change the version field to something unique.
4) Navigate in the UI to the resource that was just updated to the Content tab

Verification steps:
1)  Verify that after Step 1, the Full Package Audit Trail table, version  column has either a normal number (eg. 1.2.3) or sha256. The version  field should not be empty.
2)  Verify after Step 4 the new application has been actually deployed  on the application server. Check the file system where the application  server deploys content.
3) Verify after Step 4 the new application has RHQ-Sha256 attribute in the manifest.
4) Verify after Step 4 the content tab, history subtab has the following:
  a) Full Package Audit Trail table has the correct package information marked as Discovered, including correct version.
  b) Completed Requests table has information regarding the request submitted from the CLI, including submitted version.
Comment 2 Simeon Pinder 2012-02-10 17:44:55 EST
Moving to ON_QA as new RC 4 available to test in:
Comment 3 Mike Foley 2012-02-15 14:27:46 EST
Created attachment 562315 [details]
verification image
Comment 4 Mike Foley 2012-02-15 14:28:03 EST
uploaded image to document the verification
Comment 5 Heiko W. Rupp 2013-09-03 11:15:37 EDT
Bulk closing of old issues in VERIFIED state.

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