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 1325812

Summary: 'Run Puppet' button should be associated with REX
Product: Red Hat Satellite Reporter: Maxim Burgerhout <mburgerh>
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-06 12:09:13 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:

Description Maxim Burgerhout 2016-04-11 09:34:12 UTC
Description of problem:
For each host, we show a 'Run Puppet' button, that currently requires manual set up and does not integrate nicely with the new REX framework.

Ideally, the 'Run Puppet' functionality should just forward to the 'Run Puppet Once' job template. Otherwise, this eternally grayed out button will raise eyebrows and questions.

Considering we have the required parts in place now (SSH authentication for REX is there anyway), we could enable it (by default) by:
- editing the default /etc/foreman/settings.yaml to enable puppetrun
- editing the default /etc/foreman-proxy/settings.d/puppet.yml to:
  - set :puppet_provider to puppetssh
  - set :puppetssh_keyfile to /usr/share/foreman-proxy/.ssh/id_rsa_foreman_proxy (the key we use for REX as well)

This still doesn't integrate with REX nicely, but at least it works out of the box this way (for new hosts that have the public key).

Alternatively, the 'Run Puppet' button could be hidden and people would just rely on 'Run job'.

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

How reproducible:


Steps to Reproduce:
1. Open host page
2. Focus eyes on right most corner of white part of screen, next to 'Delete'
3.

Actual results:
'Run Puppet' button is grayed out and visible.

Expected results:
Button is either hidden on usable (preferably by default, preferably through REX)

Additional info:

Comment 1 Bryan Kearney 2016-07-26 18:59:52 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Maxim Burgerhout 2016-10-06 12:09:13 UTC

*** This bug has been marked as a duplicate of bug 1376408 ***