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.

This bug was initially created as a copy of Bug #2158510

I am copying this bug because: 

This update is to be evaluated for doc impact.

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

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/managing_hosts/index#executing-a-remote-job_managing-hosts

The existing procedure (see c#2) does not need updating; it still applies as it is.

The update described in the web UI (additional details about a rex job) doesn't need any additional explaining in the documentation.

Adam, are you okay with *not* documenting these changes? See my explanation in comment#3.

Yes, I'd be fine with that

Nothing to document here.