Bug 2214261

Summary: rex wizard should hint that it provides extended cronline expressions
Product: Red Hat Satellite Reporter: Peter Ondrejka <pondrejk>
Component: Remote ExecutionAssignee: Adam Ruzicka <aruzicka>
Status: CLOSED ERRATA QA Contact: Pavel Novotny <pnovotny>
Severity: low Docs Contact:
Priority: low    
Version: 6.14.0CC: aruzicka, lhellebr, pcreech, pnovotny, rlavi, zhunting
Target Milestone: 6.14.0Keywords: Triaged, UserExperience
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-foreman_remote_execution-10.0.6 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:19:49 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:
Attachments:
Description Flags
updated cron line with extended syntax support none

Description Peter Ondrejka 2023-06-12 11:56:39 UTC
Description of problem:
Nothing in the UI hints that there are extended cronline expressions available for scheduling rex jobs. This way, the new capability could go unnoticed

Version-Release number of selected component (if applicable):
Satellite 6.14 

Suggestions:
1. The Cronline dropdown option option for setting recurrence could be reneamed to "Cronline (extended)" or something similar. 
2. The help pop-up for the cronline field could include some of the fugit expressions for awareness

Comment 2 Adam Ruzicka 2023-06-20 14:04:03 UTC
6.14.0 would be nice or maybe 6.14.z as I wouldn't want to block the release on a purely cosmetic change. It is a just a change in wording which should be pretty straightforward to do, even if it needs to happen in multiple places.

Just a note, we can use these extended crons everywhere where recurring logics are used, which also means sync plans. Once we start adding hints about it to the ui, we should probably add it everywhere.

Comment 3 Adam Ruzicka 2023-06-20 14:27:04 UTC
Also, it would be nice if we waited for docs for this to be written and then pointed to the docs

Comment 4 Adam Ruzicka 2023-08-08 09:40:46 UTC
Created redmine issue https://projects.theforeman.org/issues/36652 from this bug

Comment 5 Bryan Kearney 2023-08-10 16:02:49 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36652 has been resolved.

Comment 7 Pavel Novotny 2023-08-21 12:47:13 UTC
Verified in 6.14 snap 12:
satellite-6.14.0-3.el8sat.noarch
foreman-3.7.0.7-1.el8sat.noarch
rubygem-foreman_remote_execution-10.0.6-1.el8sat.noarch

The (?) info tooltip now contains additional text: "The cron line supports extended cron line syntax. For details please refer to the __documentation__."
See the attached screenshot for full details.

The "documentation" link for downstream Satellite leads to online 6.14 documentation at access.redhat.com (content TBD).
For downstream Foreman, the link currently leads to https://docs.theforeman.org/3.7/Managing_Hosts/index-foreman-el.html#using-extended-cron-lines_managing-hosts

Comment 8 Pavel Novotny 2023-08-21 12:49:41 UTC
Created attachment 1984329 [details]
updated cron line with extended syntax support

Comment 11 errata-xmlrpc 2023-11-08 14:19:49 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