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.

Description of problem:

If puppetrun is not working then it seems the "Run puppet" GUI button should be removed.

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


How reproducible:


Steps to Reproduce:
1. Go to *Hosts* > *All Hosts* and select <host_name>
2. Notice "Run puppet" GUI button is not active.
3.

Actual results:


Expected results:


Additional info:

 Why puppetrun failing on Red Hat Satellite 6.1.x? — https://access.redhat.com/solutions/2162121

Can you attach a screenshot?  Also, to confirm, you are seeing this on 6.2.z?  Thanks!

Created attachment 1263289 [details]
"Run puppet" GUI button

Hello

I see this on: Version Satellite 6.2.8
foreman-1.11.0.66-3.el7sat.noarch

Sorry for omitting that info

Hello

With Peter Ondrejka's help I found out the instructions in the config files were misleading.


With Ewoud van Wijngaarden's help I got it working and submitted fixes for the config files.



Fix Instructions 
https://github.com/theforeman/puppet-foreman_proxy/pull/427


https://github.com/theforeman/smart-proxy/pull/581
Fix the instructions for puppet kick  http://projects.theforeman.org/issues/23399 

Bonus at Ewoud's suggestion:
Bug 1571815 -        [RFE] Report status of Puppet run ability in web UI
     https://bugzilla.redhat.com/show_bug.cgi?id=1571815

Returning to the default assignee to be re-triaged as the schedule allows.

Hello

Closing as DEFERRED as its not considered fully supported at present because Engineering want to make the Puppet Run button part of Remote Execution. Users can follow:

[Using the Puppet Run button to trigger Remote Execution](https://access.redhat.com/solutions/4105581)

Thank you