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.
Created attachment 1634553[details]
screenshot of notification
Description of problem:
Puppet run job notification do not populate "%{puppet_options}"' value. See attachment.
Version-Release number of selected component (if applicable):
Satellite 6.7 snap 1
How reproducible:
always
Steps to Reproduce:
1. Go to any host description page
2. Click on "Schedule remote job" drip down
3. Select "Run Puppet once"
4. See notification after job completion
Actual results:
A job 'Run Puppet once with "%{puppet_options}"' has finished successfully
Expected results:
puppet_otions should populate or A job 'Run Puppet once' has finished successfully or A job 'Run Puppet once for $hostname' has finished successfully
Additional info:
Verified on Satellite 6.8 snap 8.
Using steps from problem description I got job with name `Run puppet once with "''"`, same name is shown in notifications. Puppet options are correctly expanded.
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
Created attachment 1634553 [details] screenshot of notification Description of problem: Puppet run job notification do not populate "%{puppet_options}"' value. See attachment. Version-Release number of selected component (if applicable): Satellite 6.7 snap 1 How reproducible: always Steps to Reproduce: 1. Go to any host description page 2. Click on "Schedule remote job" drip down 3. Select "Run Puppet once" 4. See notification after job completion Actual results: A job 'Run Puppet once with "%{puppet_options}"' has finished successfully Expected results: puppet_otions should populate or A job 'Run Puppet once' has finished successfully or A job 'Run Puppet once for $hostname' has finished successfully Additional info: