I have encountered an issue with foreman and oVirt, but it part of the oVirt that causes the issue.
When a task such as delete is sent to oVirt, and there is an issue, it takes over an hour to the task to report time-out (from oVirt itself).
While this happens, foreman is not responsive (at least in development env, didn’t check if in prod mode it is responsive), forcing the restart of Puma.
I think that there should be at least the ability to set timeout for the request from the fog-ovirt and/or foreman, so that it will not take an hour to fail, but rather a given configurable timeout.
Following short discussion with @Ori_Rabin, I understand that it’s not just “hey, timeout arrived”, message, but it should have more things on it, that I’m not sure yet, what should it be.
Your thinking on the matter are more then welcome