Verified on 6.12.3 snap 1 Deleting sync plans when disabled does not disrupt foreman-maintain's ability to enable the right sync plans. Steps to Reproduce: 1. Create 2 sync plans 2. # foreman-maintain advanced procedure run sync-plans-disable 3. # hammer sync-plan delete --id 1 4. # foreman-maintain advanced procedure run sync-plans-enable Results: Running ForemanMaintain::Scenario ================================================================================ re-enable sync plans: | Total 1 sync plans are now enabled. [OK] -------------------------------------------------------------------------------- You can also see the proper list of enabled and disabled sync plans in /var/lib/foreman-maintain/data.yml
Verified in 6.12.3 snap 2 Test automation covering the following steps ran and passed successfully 1. Create 2 sync plans 2. # foreman-maintain advanced procedure run sync-plans-disable 3. # hammer sync-plan delete --id 1 4. # foreman-maintain advanced procedure run sync-plans-enable Results: Running ForemanMaintain::Scenario ================================================================================ re-enable sync plans: | Total 1 sync plans are now enabled. [OK] --------------------------------------------------------------------------------
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.12.3 Async Security 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:1630