-
Bug
-
Resolution: Done-Errata
-
Major
-
6.9.0
-
False
-
-
False
-
CLOSED
-
5,850
-
Platform
-
-
-
Important
-
Yes
Description of problem:
foreman-maintain will try to re-enable sync plans that don't exist anymore if there are references to them on the data.yml file.
Version-Release number of selected component (if applicable):
Satellite 6.9
How reproducible:
Steps to Reproduce:
1. Create 2 sync plans
2. Disable sync plans using foreman-maintain:
~~~
- foreman-maintain advanced procedure run sync-plans-disable
Running ForemanMaintain::Scenario
================================================================================
disable active sync plans:
\ Total 2 sync plans are now disabled. [OK]
--------------------------------------------------------------------------------
~~~
3. Remove one of the sync-plans
~~~
- hammer sync-plan delete --id 4
Sync plan destroyed.
~~~
4. Try enabling sync plans back:
~~~
- foreman-maintain advanced procedure run sync-plans-enable
Running ForemanMaintain::Scenario
================================================================================
re-enable sync plans:re-enabling sync plans [FAIL]
Could not update the sync plan:
Could not find sync_plan resource with id 4. Potential missing permissions: edit_sync_plans
--------------------------------------------------------------------------------
Scenario [ForemanMaintain::Scenario] failed.
The following steps ended up in failing state:
[sync-plans-enable]
Resolve the failed steps and rerun
the command. In case the failures are false positives,
use --whitelist="sync-plans-enable"
~~~
Actual results:
Fail to re-enable sync plans
Expected results:
All valid sync plans would be enabled
Additional info:
BZ#1717020 was about the exact same thing and is supposed to be fixed on 6.6, however we can see it in 6.9.
- external trackers
- links to