Bug 1311526 - content view and repository history and tasks should contain details
Summary: content view and repository history and tasks should contain details
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.0.4
Hardware: Unspecified
OS: Unspecified
high vote
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Jitendra Yejare
URL: http://projects.theforeman.org/issues...
Depends On:
TreeView+ depends on / blocked
Reported: 2016-02-24 12:11 UTC by Tom McKay
Modified: 2019-09-25 21:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2016-07-27 09:23:17 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13734 0 None None None 2016-04-22 15:56:44 UTC
Red Hat Product Errata RHBA-2016:1501 0 normal SHIPPED_LIVE Red Hat Satellite 6.2 Capsule and Server 2016-07-27 12:28:58 UTC

Description Tom McKay 2016-02-24 12:11:40 UTC
The content view history as well as the export tasks should show enough information: user, time, cvv

Comment 1 Tom McKay 2016-02-24 12:11:42 UTC
Created from redmine issue http://projects.theforeman.org/issues/13734

Comment 2 Tom McKay 2016-02-24 12:11:46 UTC
Upstream bug assigned to tomckay@redhat.com

Comment 4 Bryan Kearney 2016-02-26 17:06:24 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/13734 has been closed
Thomas McKay
Applied in changeset commit:katello|9d9c4ead645355f346ace7a3fa0c811510ea0741.

Comment 5 Jitendra Yejare 2016-03-22 09:50:25 UTC
Verified in Sat 6.2 snap 4.

The issue is no more reproducible.

I can see the content view export details in CV History with time(in UTC), cv version and user  plus addition action and status.

So , changing the state to Verified.

Comment 8 errata-xmlrpc 2016-07-27 09:23:17 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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