During the final stages of leapp 8to9 upgrade (already booted to upgraded RHEL9), one is instructed to remove excludes and remove leap packages (chapter 7 in documentation) :

# dnf config-manager --save --setopt exclude=''
# dnf remove $(rpm -qa | grep \.el[78] | grep -vE 'gpg-pubkey|libmodulemd|katello-ca-consumer')
# dnf remove leapp-deps-el9 leapp-repository-deps-el9 

However, this can still be done while leapp_resume.service is still running, resulting in its failure:

2025-09-23 13:34:46.850 INFO     PID: 1072 leapp: Resuming execution after phase: Finalization
...
2025-09-23 13:36:18.316 INFO     PID: 1072 leapp.workflow.FirstBoot: Executing actor enable_rhsm_target_repos
2025-09-23 13:36:18.575 ERROR    PID: 1072 leapp.workflow.FirstBoot: Actor enable_rhsm_target_repos has crashed: None
Sep 23 13:36:18 fastvm-rhel-8-10-155 leapp3[8606]: FileNotFoundError: [Errno 2] No such file or directory: '/etc/leapp/repos.d/system_upgrade/common/actors/enablerhsmtargetrepos'

The `dnf remove` was executed at 13:36:01
The official documentation does not mention that there might be service still running and that the packages should not be removed yet.

Possible solution:
Introduce actor which will remove exclude= of leapp/snactor packages in dnf.conf after Finalization step and remove "exclusion" from documentation. This way the leapp packages cannot be removed while there is still work to be done, and mention that in documentation to prevent confusion.