Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1622196

Summary: Content view -> History -> Action column is broken when foreman tasks are deleted
Product: Red Hat Satellite Reporter: sthirugn <sthirugn>
Component: Content ViewsAssignee: Swetha Seelam <sseelaml>
Status: CLOSED CURRENTRELEASE QA Contact: Lai <ltran>
Severity: medium Docs Contact:
Priority: high    
Version: 6.3.2CC: andrew.schofield, bkearney, jturel, kabbott, sthirugn, walden
Target Milestone: UnspecifiedKeywords: PrioBumpField, PrioBumpPM, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-10-17 16:45:11 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:
Description Flags
content view history action column
none
Content view versions status column none

Description sthirugn@redhat.com 2018-08-24 16:57:05 UTC
Created attachment 1478589 [details]
content view history action column

Description of problem:
Content view -> History -> Action column is broken when foreman tasks are deleted

Version-Release number of selected component (if applicable):
Satellite 6.3.2

How reproducible:
Always

Steps to Reproduce:
1. Create a content view, publish, promote
2. Go to the content view page -> select the content view -> History tab
3. Review the Action column, it displays fine.
4. Delete foreman-tasks (Caution: the below command removes all foreman tasks)
foreman-rake foreman_tasks:cleanup TASK_SEARCH='label ~ *' AFTER='0d' VERBOSE=true

Actual results:
The Action column is broken after the foreman-tasks are deleted, displaying 
`{{ actionText(history) }}`

Expected results:
The action column should display normally after foreman tasks are deleted.

Additional info:

Comment 1 sthirugn@redhat.com 2018-08-24 16:57:51 UTC
the url which is used to display this page is:
https://satellite.example.com/content_views/2/history?page=1&per_page=20&sortBy=created_at&sortOrder=DESC

Comment 3 sthirugn@redhat.com 2018-08-24 17:08:37 UTC
Created attachment 1478590 [details]
Content view versions status column

Comment 4 sthirugn@redhat.com 2018-08-24 17:09:54 UTC
Also note that in https://satellite.example.com/content_views/2/versions?page=1&per_page=20 page (screenshot: content_view_versions_Status_column.png), the Status column in broken.

Version 2.0 shows `Published` in Status column and this information is missing in Version 1.0 since the corresponding foreman tasks were deleted.

Comment 6 Walden Raines 2018-08-26 07:59:49 UTC
Are there any javascript errors that occur when this happens?

It looks like angular isn't evaluating the these fields at all which makes me think that there is some JS error.