Foreman Maintain

Imagine, that the data.yml has the following data:


[root@or ~]# cat /var/lib/foreman-maintain/data.yml
---
:default:
:sync_plans:
:enabled: []
:disabled:
- 2


Now, you go to the sync-plan UI page, and delete the sync plan with id '2'.
If you now try to do a offline backup, it will fail because hammer tries to "enable" the sync-plan with id 2 - which was deleted before.

The root cause of this, that the code doesn't validate, that the IDs of the sync-plan still exist in the DB.