Bug 2171180

Summary: Reasons for not deleting the manifest don't apply with SCA enabled
Product: Red Hat Satellite Reporter: Taft Sanders <tasander>
Component: Subscription ManagementAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: Sam Bible <sbible>
Severity: low Docs Contact:
Priority: medium    
Version: 6.12.1CC: ahumbe, chrobert, pcreech, sbible
Target Milestone: 6.14.0Keywords: EasyFix, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-08 14:18:33 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:
Attachments:
Description Flags
manifest delete warning none

Description Taft Sanders 2023-02-18 19:54:07 UTC
Created attachment 1944958 [details]
manifest delete warning

Description of problem:
When deleting a manifest on a Satellite, the user is prompted with a warning before deleting the manifest and all the reasons its a bad idea. With SCA enabled, a lot of these reasons are invalid.

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

How reproducible:
Every time

Steps to Reproduce:
1. Delete the manifest from a Satellite on the WebUI
2.
3.

Actual results:
The user is prompted by a warning about all the bad things that will happen if they delete the manifest. See screenshot attached

Expected results:
When SCA is enabled, these warnings should be changed or reworded.

Additional info:
Below are the actions in order from the screenshot addressed:

"Delete all subscriptions that are attached to running hosts"
This is not true and not applicable. Any custom subscriptions wouldn't be deleted, only Red Hat subscriptions. But with SCA enabled, you don't have subscriptions on hosts. In fact, you can't even change your subscription on the Host > Content Host page of a client if you wanted to. The tab for subscriptions is removed from the host once SCA is enabled.

"Delete all subscriptions attached to activation keys"
That tab is also removed with SCA enabled.

"Disable Red Hat Insights"
If you have a subscription providing smart management and you are using insights on your clients, then yes while the subscription is removed from the Satellite, Insights uploads will not be sent until the new subscription containing smart management is added back. But it won't disable it forcing a user to have to re-enable something afterward.

"Require you to upload the subscription manifest and re-attach subscriptions to hosts and activation keys"
Yes, you will have to upload a new manifest, which is typically why one would delete the manifest unless they are just testing buttons to see what they do.

Comment 1 Chris Roberts 2023-05-30 14:48:54 UTC
Let's keep, should be easy to fix.

Comment 2 Jeremy Lenz 2023-07-18 17:57:54 UTC
Created redmine issue https://projects.theforeman.org/issues/36604 from this bug

Comment 3 Bryan Kearney 2023-07-18 20:02:59 UTC
Upstream bug assigned to jlenz

Comment 4 Bryan Kearney 2023-07-18 20:03:02 UTC
Upstream bug assigned to jlenz

Comment 5 Bryan Kearney 2023-07-20 00:02:51 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36604 has been resolved.

Comment 7 Sam Bible 2023-08-10 14:53:42 UTC
Verified on 6.14 - Snap 10

Steps to verify:

1. Upload a manifest to both an SCA and non SCA org
2. Attempt to delete a manifest in both of them

Expected Results:
You see different, appropriate messages depending on the type of manifest.

Actual Results:
You see different, appropriate messages depending on the type of manifest.

Comment 10 errata-xmlrpc 2023-11-08 14:18:33 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.14 security and bug fix update), 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-2023:6818