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 2158510

Summary: [RFE] Job review details should contain scheduling information
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Remote ExecutionAssignee: Maria <magaphon>
Status: CLOSED ERRATA QA Contact: Lukáš Hellebrandt <lhellebr>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: aruzicka, lhellebr, magaphon
Target Milestone: 6.14.0Keywords: FutureFeature, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-10.0.0 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:18:10 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 Peter Ondrejka 2023-01-05 15:51:22 UTC
Description of problem:
In the new Rex wizard, the Review page does not contain details about future execution or recurring execution settings.

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

How reproducible:
always

Steps to Reproduce:
1. Schedule a rex job through new UI wizard
2. Set either future or recurring execution and specify some details on the related steps (e.g. starts at, ends after x occurrences...)
3. Get to the last step, almost all settings are listed but these scheduling details are not

Comment 3 Lukáš Hellebrandt 2023-07-12 13:31:44 UTC
Verified with Sat 6.14.0 snap 6.0, rubygem-foreman_remote_execution-10.0.3-1.el8sat.noarch.

When scheduling the task, the last step now contains:

FOR IMMEDIATE:
Schedule type: Immediate execution
Recurrence: Does not repeat

FOR FUTURE:
Schedule type: Future execution
Recurrence: Does not repeat
Starts at: Wed Jul 12 2023 14:27:00 GMT+0200 (Central European Summer Time)

FOR RECURRING USING CRON:
Schedule type: Recurring execution
Recurrence: Cronline
Starts: Now
Repeats: Cron line - /1 * * * *
Ends: Never
Purpose:

FOR RECURRING USING FORM:
Schedule type: Recurring execution
Recurrence: Weekly
Starts: Mon Jul 24 2023 14:23:00 GMT+0200 (Central European Summer Time)
Repeats: Every week on Sun, Mon at 14:24
Ends:Mon Jul 31 2023 14:22:00 GMT+0200 (Central European Summer Time)
Purpose: test

WHEN RESCHEDULING:
Review in the same format as for immediate execution because only the single run is being rescheduled (unless manually specified otherwise during rescheduling).

Comment 6 errata-xmlrpc 2023-11-08 14:18:10 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.14 security and bug fix update), 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-2023:6818