Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Assuming that one system can belong to multiple system-groups. So while removing a system group with associated systems, and same system is associated with other system group, UI should raise a proper warning message.


Version-Release number of selected component (if applicable):
katello-0.2.44-1.git.73.3737e93.el6_3.noarch

How reproducible:
always

Steps to Reproduce:
1. Register 'systemA' 
2. Create a system group 'sysgrp1'
3. Add 'systemA' to sysgrp1.
4. Create another system group 'sysgrp2'
5. Add 'systemA' to 'sysgrp2'
6. Now remove sysgrp1 along with associated systemA
  
Actual results:
UI simply remove the system group and associated system.

Expected results:
UI should raise a warning message/validation error that the same system is associated with other system group

Additional info:

this is working as designed, mass-deletion already has a warning dialog and we should not block the deletion because the systems exist in another group.

getting rid of 6.0.0 version since that doesn't exist