The behavior depends on a task: it shows the progress of the task. If the task runs for too long, it will appear as the command is hanging. Eventually it will stop, but it will take a long time. Workaround: you can always press CTRL+C to stop the hammer command, the asynchronous task will continue running in the background. Is it acceptable?
Hi Shimon, As you said the process is taking too much time, but it's too much for removing a package, I can assume this behavior is affected by bug https://bugzilla.redhat.com/show_bug.cgi?id=1457977 but it should have a reasonable timeout to exit as other tasks do. Any way we have fixed our automation to cancel such process when reaching a time limit (as the whole automation was hanging on that tests), but in a client environment it can appear annoying and not acceptable.
@dlezzoum Thanks for the quick reply, after digging a bit into the code I have fond the following things that could help here: 1. Content tasks have a timeout setting - look for content_action_finish_timeout setting in the Administer -> Settings UI section (it's called "Finish action timeout" in the content tab). 2. You can add --async in the hammer command to release the execution: # hammer host package-group remove --help Usage: hammer host package-group remove [OPTIONS] Options: --async Do not wait for the task Is it good enough?
Hi Shimon, many thanks for the explanation. Yes I think it's good enough.
Based on comments, I'm closing as notabug