Bug 1940396 - [RFE] Introduction of GUI based option to be able to bulk select and remove Content View versions in Red Hat Satellite 6
Summary: [RFE] Introduction of GUI based option to be able to bulk select and remove C...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.9.0
Hardware: All
OS: All
high
medium
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
: 1995374 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-18 11:07 UTC by Sayan Das
Modified: 2024-03-25 18:14 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:32:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 34169 0 Normal Closed Allow bulk selections on CV UI to support bulk removing versions 2022-03-15 12:33:44 UTC
Red Hat Issue Tracker SAT-3311 0 None None None 2022-08-22 07:14:53 UTC
Red Hat Knowledge Base (Solution) 2760531 0 None None None 2021-04-08 17:28:24 UTC
Red Hat Knowledge Base (Solution) 3966701 0 None None None 2021-04-08 17:28:24 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:32:36 UTC

Description Sayan Das 2021-03-18 11:07:38 UTC
1. Proposed title of this feature request

GUI-based option to be able to bulk select and remove Content View versions.

2. What is the nature and description of the request?

Content View version cleanup is one of the important maintenance activities that most of the users perform and they rely upon loop using hammer command or they delete the versions one by one. None of these methods are user-friendly. So there should be a way to select the required versions of a CV using checkboxes and delete them in bulk from UI only.


3. Why does the customer need this? (List the business requirements here)

For better and easier maintenance of content-view versions. 

These are the currently available options for the customers.

https://access.redhat.com/solutions/2760531 or https://access.redhat.com/solutions/3966701 --> Both use the hammer and do not leaves the user with much of a choice for selective deletion and when too many versions are there hammer operation for delete will be way too slow for each version.

redhat.satellite.content_view_version_cleanup role from ansible collections --> Although it's designed well We should not expect that every customer will be using ansible collections to manage satellite or will have the necessary knowledge to do so.

So there should be a way to select the required versions of a CV using checkboxes and delete them in bulk from UI only.



4. How would the customer like to achieve this? (List the functional requirements here)

From Satellite UI --> Content --> Content Views, 
- Open a CV and go to the versions tab
- Select the version we want to delete using a checkbox
- From the select action dropdown click on “Delete Selected Versions” 
- It should create an async bulk task and display the task ID to the user.

This will provide a much better product experience than that of any other available options.



5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
- Build a Satellite.
- Create a CV and publish it more than 10 times
- Keep Library environment promoted to latest version 10.0 and Prod LCE promoted to version 6.0
- Select all versions except 10.0 and 6.0 and from the bulk option, Delete the same.

6. Is there already an existing RFE upstream or in Red Hat Bugzilla?

NA


7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

Suggested in Satellite 6.9.z or beyond


8. Is the sales team involved in this request and do they have any additional input?
No.


9. List any affected packages or components.

katello


10. Would the customer be able to assist in testing this functionality if implemented?
NA but support delivery team can

Comment 3 Brad Buckingham 2021-08-19 12:09:05 UTC
*** Bug 1995374 has been marked as a duplicate of this bug. ***

Comment 5 Bryan Kearney 2022-03-14 20:03:55 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34169 has been resolved.

Comment 9 Lai 2022-08-04 19:14:20 UTC
Steps to test:
1. Create a cv
2. Publish cv for at least 10 versions
3. Go to cv and go to versions tab
4. Select a few versions to delete
5. Go to the kebab next to the search bar and select 'delete'
6. Repeat 1 - 6 with custom repos and rhel repos added to the cv

Second set of testing
1. Create a PROD LCE to be promoted
2. Create a cv
3. Publish the CV with promoted environment to PROD LCE all the way to version 6.0
4. Continue publishing the CV, but from version 7-10 only in Library environment
5. Go to versions tab in the cv
6. Select all versions except 10.0 and 6.0 and select the kebab next to the search bar and select 'delete'
7. Repeat steps 1-6 with custom repos and rhel repos added to the cv

Expected result:
First set of testing:
5 - 6. UI should show the version being deleted and all selected version should be deleted successfully. 

Second set of testing:
5 - 6. UI should show the version being deleted and all selected version should be deleted successfully.

Actual Result:
First set of testing:
5 - 6. UI does show the version being deleted and all selected version are deleted successfully. 

Second set of testing:
5 - 6. UI does show the version being deleted and all selected version are deleted successfully.

Verified on 6.12 snap 4

Comment 14 errata-xmlrpc 2022-11-16 13:32:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: Satellite 6.12 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:8506


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