Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 877688

Summary: ListRemoveSystems.do System Set Manager selection
Product: [Community] Spacewalk Reporter: Curtis <curtis>
Component: WebUIAssignee: Tomas Lestach <tlestach>
Status: CLOSED DUPLICATE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.7CC: jpazdziora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-19 09:21:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1484117    

Description Curtis 2012-11-17 21:34:26 UTC
Description of problem:
On the ListRemoveSystems.do page when a system(s) checkbox is selected the Systems Set Manager section in the top right corner of the page does not register the system(s) as manageable.  This action functions under a Systems list, but not in the Systems Group list.  

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

How reproducible:
This has been tested on multiple systems.

Steps to Reproduce:
1.Go to a system group under System Groups.
2.Select a system or systems by clicking their checkbox.
3.The number of managed systems in the top right corner does not change. It remains 'No Systems Selected'.  Systems are not listed in Systems Set Manager.
  
Actual results:
The number of managed systems in the top right corner does not change. It remains 'No Systems Selected'.  Systems are not listed in Systems Set Manager.

Expected results:
Selected systems under Systems Groups should be registered by System Set Manager.

Additional info:

Comment 1 Jan Pazdziora (Red Hat) 2012-11-19 09:21:49 UTC

*** This bug has been marked as a duplicate of bug 877685 ***

Comment 2 Eric Herget 2017-09-28 17:56:55 UTC
This BZ closed some time during 2.5, 2.6 or 2.7.  Adding to 2.7 tracking bug.