Bug #11272

bulk delete of hosts redirect to tasks progress page

Added by Ohad Levy about 6 years ago. Updated about 2 years ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


As a user, when I delete multiple hosts, I'm redirected to a foreman-tasks show page. I was expecting to get back to the host list, or maybe a customized view for deleting hosts.

on top of that, the page does not auto reloads, which makes the user stare at a progress bar that never update it self.

further, i had a failure in one host deleting task (the compute resource was not reachable) in either case, it was very challenging to find the root cause of failure, and imho that should made more visible instead of searching though the sub tasks.

Related issues

Related to Katello - Tracker #8161: Host UnificationRejected


#1 Updated by Eric Helms about 6 years ago

  • Status changed from New to Need more information
  • Triaged changed from No to Yes

I think there are two issues here:

1) Whether or not we should be redirecting to the tasks page for all initiated tasks.
2) Whether the task details is sufficient for diagnosing an issue

For #1, we have either defaulted to sending the user to the task details page when kicking off an action that includes a task or embedded the task details within the current page such as if you go initiate a sync from the repository details page. Would the latter behavior be more in line with what you expect?

For #2, I think that might need to be an RFE filed against foreman_tasks.

#2 Updated by Eric Helms almost 6 years ago

  • Legacy Backlogs Release (now unused) set to 114

#3 Updated by Eric Helms almost 6 years ago

#4 Updated by John Mitsch about 2 years ago

  • Target version deleted (Katello Backlog)
  • Status changed from Need more information to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF