Created from redmine issue https://projects.theforeman.org/issues/23927
Upstream bug assigned to jsherril
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/23927 has been resolved.
Answers: =================================================================================== Bug #24733: [Sync-plans] Sync plans created with start date in the past schedule a lot of dynflow tasks Create a sync plan with start date one day before, check that this is not allowed. ANS: Agreed ----------------------------------------------------------------------------- Bug #23928: Migrate sync plans to recurring logics Please help me here. ANS: Test that, after upgrade, sync plans still have recorring logic and that the sync plans work ----------------------------------------------------------------------------- Feature #23929: Specify custom cron syntax for sync plans Create custom sync plan with interval set to custom cron, say every ten minutes, save, check after 33 minutes or more that multiple syncs occurred as expected. ANS: Agreed, Test only after upgrade, as this is Sat6.5 only. ----------------------------------------------------------------------------- Bug #22961: re-vamp upgrade proccess to not require installer updates ANS: this is covered by the test for "Migrate sync plans to recurring logics" ----------------------------------------------------------------------------- Feature #23888: support enable/disable recurring logics ANS: Test enabling/disabling sync plans from the sync plan page. Also test enable/disable recurring logics on the monitor > recurring logics page ----------------------------------------------------------------------------- Refactor #21938: Single upgrade rake task ANS: this is covered by the test for "Migrate sync plans to recurring logics" ----------------------------------------------------------------------------- Refactor #24189: Update katello to use foreman upgrade task ANS: this is covered by the test for "Migrate sync plans to recurring logics" ----------------------------------------------------------------------------- Bug #24671: [Sync-plans] Remove dead code Ans: No tests needed ----------------------------------------------------------------------------- Bug #24828: add sync-plan upgrade task to new upgrade process ANS: this is covered by the test for "Migrate sync plans to recurring logics" ----------------------------------------------------------------------------- Bug #24818: [Sync-plans] Sync plan save button continues to be in working mode after error Enter invalid plan, check that save button does not allow you to save? But in what way invalid? I found "reproduce" steps here:https://github.com/Katello/katello/pull/7723 ANS: try creating a sync plan with: duplicate name invalid cron syntax verify that error shows up, and that youc an correct the issue and still save the sync plan ----------------------------------------------------------------------------- Bug #24901: [Sync-Plans] Clear cron expression when interval is not custom cron Create custom sync plan with interval set to custom cron, save, change interval to something else, save, select custom cron interval and confirm custom cron field is clear. Enter an invalid cron expression, save, check that error "Cron expression is not valid!" is displayed. ANS: agreed.
Hello Bug 1694727 - Main Recurring logics page does not display recurring logic ID
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, 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-2019:1222