History | Log In     View a printable version of the current page.  

jira.rhq-project.org has been archived and is now in read-only mode.

All issues have been moved to bugzilla.redhat.com. All new issues or updates to existing issues should be made through bugzilla.
Specific old RHQ issues can be found using a query of this form: https://bugzilla.redhat.com/show_bug.cgi?id=RHQ-1999.
New bugs can be raised here. Accounts at bugzilla.redhat.com have been created for existing RHQ users.
Open bugs raised in the last week can be found here.
Issue Details (XML | Word | Printable)

Key: RHQ-57
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Jason Dobies
Reporter: Jason Dobies
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

Display package audit trail in the UI

Created: 10/Mar/08 01:25 PM   Updated: 06/Aug/08 09:14 AM
Component/s: FX - Content
Fix Version/s: 1.1

Time Tracking:
Not Specified

Resolution Date: 22/Jul/08 01:55 PM
Date of First Response: 21/Jul/08 12:15 AM
Tester: Corey Welton
VCS Revision: 1,131


 Description  « Hide
There's no place where we simply show a filterable list of all the package audit trail for a resource. We have the data and should make it available.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joseph Marques - 21/Jul/08 12:15 AM
this might be out-of-date. does the packages > history sub-tab take care of this? if not, please reopen jdob.

Jason Dobies - 22/Jul/08 01:50 PM
r1131 - Added full package audit trail to package tab's history page. Each item can be drilled into for more detail.

Jason Dobies - 22/Jul/08 01:55 PM
The audit trail appears on the bottom of the history sub-page of the packages tab. It will have entries to reflect everything going on in the package subsystem, including package discoveries, creation requests, and the results of those requests.

QA:

The QA for this largely revolves around poking around the content subsystem. After the initial resource import, or put another way once packages appear under the deployed subtab, there should be entries in the audit trail to indicate that a package was discovered on the resource. Deploying a package should also add the appropriate entries to the audit trail.

When there are no entries in the audit trail, the table contains a message reflecting that state. This is most easily seen by inventorying a JBoss AS instance and quickly checking the package's history page before the package discovery has a chance to take place.

Corey Welton - 06/Aug/08 09:14 AM
Verified -

Prior ot anything in the audit trail, user is told there are no events; afterw deploying packages, their deployment status shows up correctly in the audit trail.