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 1770544 - Puppet run job notification do not populate "%{puppet_options}"' value
Summary: Puppet run job notification do not populate "%{puppet_options}"' value
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Notifications
Version: 6.7.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.8.0
Assignee: Amir
QA Contact: Peter Dragun
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-11-10 11:29 UTC by Nikhil Kathole
Modified: 2023-12-15 16:55 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-foreman_remote_execution-3.1.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 12:59:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of notification (18.38 KB, image/png)
2019-11-10 11:29 UTC, Nikhil Kathole
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 28997 0 Normal Closed Puppet run once job's format_description should remove %{puppet_options} 2020-12-15 17:40:45 UTC
Red Hat Product Errata RHSA-2020:4366 0 None None None 2020-10-27 12:59:38 UTC

Description Nikhil Kathole 2019-11-10 11:29:40 UTC
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:

Comment 7 Walden Raines 2019-11-15 20:12:38 UTC
Created redmine issue https://projects.theforeman.org/issues/28277 from this bug

Comment 8 Bryan Kearney 2019-11-15 21:01:01 UTC
Upstream bug assigned to afeferku

Comment 9 Tomer Brisker 2020-02-13 15:53:22 UTC
Connecting redmine issue https://projects.theforeman.org/issues/28997 from this bug

Comment 12 Bryan Kearney 2020-03-09 22:01:12 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28997 has been resolved.

Comment 13 Peter Dragun 2020-07-21 12:15:12 UTC
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.

Comment 17 errata-xmlrpc 2020-10-27 12:59:24 UTC
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


Note You need to log in before you can comment on or make changes to this bug.