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 1425519 - [RFE] Scheduled Job Templates should be named and logged appropriately
Summary: [RFE] Scheduled Job Templates should be named and logged appropriately
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.7
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-21 16:08 UTC by Josh Preston
Modified: 2018-09-04 19:07 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 19:07:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 24152 0 None None None 2018-07-04 08:36:02 UTC

Comment 1 Josh Preston 2017-02-21 16:11:19 UTC
4. Why does the customer need this? (List the business requirements here)  

   During a scheduled patch window, timely and less burdensome reporting is required to accommodate a change window.

    5. How would the customer like to achieve this? (List the functional requirements here)  

    When viewing the queued items from the jobs page, they would be named more meaningfully.

    6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
  N/A
      
    7. Is there already an existing RFE upstream or in Red Hat Bugzilla? 
   No

     
    8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?
   No  
 
    9. Is the sales team involved in this request and do they have any additional input? 
   Yes
      
    10. List any affected packages or components.  
   NA
       
    11. Would the customer be able to assist in testing this functionality if implemented?
   Yes

Comment 2 Ivan Necas 2017-02-21 16:37:19 UTC
Would including the search query inside the job listing table solve the current issue?

Comment 3 Ivan Necas 2017-02-21 16:39:09 UTC
It's also possible to specify custom description on per-job invocation bases in the advanced fields, if that's something the user is looking for

Comment 4 Josh Preston 2017-02-21 18:29:14 UTC
RE: #2

Possibly, will need to confer with customer for clarification.

RE: #3

In the meantime, they will try the advanced fields suggestion.  Will confirm with customer and consultant if this is adequate.

--

I think the customer's general theme is that during a large maintenance period, they need better operational visibility into the job tasks.  Naming them is one appropriate method, but there might be others perhaps by groupings of host collections, etc.

Comment 7 Adam Ruzicka 2018-06-19 08:52:46 UTC
Was there any feedback from the customer or the consultant?

Comment 8 Josh Preston 2018-06-25 16:42:49 UTC
The general feedback was that while the additional reporting was desired, the performance of the Satellite led operations tasks were better performed in another automation tool, namely Ansible.

There were several problems with using Satellite tasks that were easily remedied bypassing Satellite.

Comment 9 Adam Ruzicka 2018-07-04 08:36:00 UTC
Created redmine issue http://projects.theforeman.org/issues/24152 from this bug

Comment 10 Bryan Kearney 2018-09-04 18:56:54 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.

Comment 11 Bryan Kearney 2018-09-04 19:07:38 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.


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