One should prefer looking at the issues (errors tab in the task),
trying to fix the the cause of the problem (if possible), and
resume the task.
The reason why resuming is preferred is because the system might be
in inconsistent state, when some tasks hasn't finished.
Resuming is a safe operation, so one can try that and see if the task continued or caused some error.
There are the unlock operations, that can you help proceeding with other tasks
and avoid the locking, but they should be used with real caution, and I wouldn't recommand
to use them except some limited amount of tasks that don't have a risk of causing inconsistency,
such as repo sync or package install actions.
For things like repository deleting, I would recommand to make sure the task finishes successfully,
as otherwise, there might be some leftovers stay there, causing errors later, e.g. when you
try to create a repository with the same name.
Btw. the latest foreman-tasks getting released with foreman 1.9/katello 2.3 will have better handling
of the sync tasks errors, as well as bulk resume feature.
----- Original Message -----
> Hello there,
> foreman 1.8.2
> katello 2.2.1
> on RHEL 7
> - I have a repo that I would like to remove, but it's in an error state.
> - I have repos that can't sync because of locked resources.
> - sync plans are failing because of locked resources.
> - unlocking resources doesn't change the task state.
> - force unlocking doesn't change the error state.
> this is whether I do all the repos at once or if I do them singularly. Is
> there a way to remove the zombie tasks or unlock the resources and clear
> those errors?
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to firstname.lastname@example.org.
> To post to this group, send email to email@example.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.