On Mon, Nov 26, 2018 at 1:39 PM Stefano Stagnaro <
stefa...@prismatelecomtesting.com> wrote:
[snip]
> The job is hanged since user has killed fallocate process on the host.
> However, I can't kill task from the hosts itself since vdsm-client returns
> zero task on any host:
>
> # vdsm-client Host getAllTasksInfo
> {}
>
> How can I deal with it? I already tried to restart ovirt-engine.service
> but task is still there and prevent me to put the involved storage domain
> into maintenance.
>
> I also tried the "clear" method for service "job" via RestAPI but it fails
> since it's not an external job.
>
> Thank you,
> --
> Stefano Stagnaro
>
>
I think in these cases you have to use taskcleaner.sh
Last year I had similar problems with hung tasks and I was pointed to
taskcleaner.sh from Fred:
https://lists.ovirt.org/pipermail/users/2017-November/085194.html
but it was not so user friendly in its syntax
During engine-setup there are cleaning stages when you see
[ INFO ] Cleaning async tasks and compensations
[ INFO ] Unlocking existing entities
So one chance could be to run
engine-setup --offline (to prevent updates)
and let it do the clean stage
Putting environment into global maintenance before in case of self hosted
engine
There are also detailed docs on rh portal, such as
https://access.redhat.com/solutions/500263
but they need subscription for access.... and for pure oVirt I only found
this:
https://www.ovirt.org/develop/developer-guide/db-issues/helperutilities/
It would be nice to have a free documentation entry point for oVirt users
facing this kind of problems, in my opinion.
HIH,
Gianluca
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/STHMCOQPG5Z5BMJ4QIN2B44DV2MUIOSD/
