Project

General

Profile

Bug #9577

All Hosts - Bulk Action - Delete throws error Dependent Content Host

Added by Justin Sherrill about 8 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Hosts
Target version:
Difficulty:
easy
Triaged:
Yes
Bugzilla link:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1192730
Description of problem: When selecting a single or multiple hosts on the All Hosts page and selecting the Bulk Action/Select Action - Delete Hosts item, WebUI throws error "Cannot delete record because of dependent content_host"

Version-Release number of selected component (if applicable):
6.0.7

How reproducible:
Always

Steps to Reproduce:
1. Navigate to Hosts -> All Hosts
2. Select one or more hosts using the checkbox
3. Select Delete Hosts from the Select Action button pull-down
4. Confirm request in resulting dialog

Actual results:
Cannot delete record because of dependent content_host

Expected results:
Selected hosts should be deleted.

Additional info:
When selecting Delete from the "Table Button" marked Edit by default, delete works as expected.

Associated revisions

Revision 6040e333 (diff)
Added by Justin Sherrill about 8 years ago

fixes #9577 - fixing host single and bulk delete

single host delete was broken due to content host AR destroy being
moved to finalize in dynflow
multi host delete was never actually implemented in dynflow

Revision 1e07de2b
Added by Justin Sherrill about 8 years ago

Merge pull request #5059 from jlsherrill/9577

fixes #9577 - fixing host single and bulk delete

History

#1 Updated by The Foreman Bot about 8 years ago

  • Status changed from New to Ready For Testing
  • Target version set to 67
  • Pull request https://github.com/Katello/katello/pull/5059 added
  • Pull request deleted ()

#2 Updated by Justin Sherrill about 8 years ago

  • Category changed from Web UI to 83
  • Legacy Backlogs Release (now unused) set to 23
  • Difficulty set to easy
  • Triaged changed from No to Yes

#3 Updated by Justin Sherrill about 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

Also available in: Atom PDF