Bug 1976178 - Unable to Un-assign scap policy from all the client system using bulk action.
Summary: Unable to Un-assign scap policy from all the client system using bulk action.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: SCAP Plugin
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-25 12:28 UTC by Jaskaran Singh Narula
Modified: 2023-07-25 11:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19137 0 None None None 2023-07-25 11:32:01 UTC

Description Jaskaran Singh Narula 2021-06-25 12:28:52 UTC
Description of problem:
Using the bulk action from all hosts page, satellite UI does allow to select all the hosts in case if there are multiple pages. 

This action is required to unassign the scap policy. The Satellite UI changes whereas for hosts the host presents only on 1 page can get selected but not for all the pages.   

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

How reproducible:
100% 

Steps to Reproduce:
>> Satellite Web UI >> Hosts >> All Hosts >> Select all hosts for all the pages >> Select Action >> Unassign Compliance Policy >>> Unable to select all the hosts at this point. 

 

Actual results:
If the All hosts page has 20 hosts, it allows to select all the hosts but if there are multiple pages then this action is not possible. 

Expected results:
Ability to select all the hosts at once to remove the scap policy. 

Additional info:

Comment 3 Brad Buckingham 2023-07-21 21:06:39 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.


Note You need to log in before you can comment on or make changes to this bug.