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.

Created attachment 1710530 [details]
Screen

Description of problem: Run action is missing at job template index page


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


How reproducible: Always


Steps to Reproduce:
1. Go to Hosts -> Job Templates
2. "Run" is missing in Action column

Actual results:  "Run" action is missing


Expected results:  Should be able run job template


Additional info:
[root@dhcp131-3 ~]# rpm -qa satellite
satellite-6.8.0-0.7.beta.el7sat.noarch
rp[root@dhcp131-3 ~]# rpm -qa foreman
foreman-2.1.0.1-1.el7sat.noarch
[root@dhcp131-3 ~]# rpm -qa katello
katello-3.16.0-0.4.rc4.el7sat.noarch

Created redmine issue http://projects.theforeman.org/issues/30685 from this bug

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30685 has been resolved.

Adam, is it possible to backport this fix to the 3.3 line and release upstream?

I was planning on releasing it tomorrow or on Monday in the worst case scenario

Verified on Satellite 6.8 snap 14

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 (Important: Satellite 6.8 release), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2020:4366