Bug 2055513
Summary: | Deletion of Custom repo deletes it from all versions of CV where it is included but the behavior is different for Red Hat based repos in Satellite 7.0 | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
Component: | Repositories | Assignee: | Samir Jha <sajha> |
Status: | CLOSED ERRATA | QA Contact: | Cole Higgins <chiggins> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.11.0 | CC: | ahumbe, ehelms, iballou, mdolezel, pcreech, sajha, satellite6-bugs |
Target Milestone: | 6.11.0 | Keywords: | Triaged, UserExperience |
Target Release: | Unused | ||
Hardware: | All | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tfm-rubygem-katello-4.3.0.19-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-07-05 14:33:19 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: |
Description
Sayan Das
2022-02-17 06:50:52 UTC
I confirm that: If we don't try to disable the Red Hat repo but try to delete it from the Content --> Products page, that deletes the repo from every published version of CV or CCV as well as disables it. So the behavior of deletion for custom and RH repos are the same. But this is a big change and we should not expose it directly as a default option. My suggestion is the following : For Product: Have a global settings inside Administer --> Settings --> Content that will be disabled by default i.e. will not allow\use remove_from_content_view_versions=true with DELETE API but if that is manually turned on, Then "remove_from_content_view_versions=true" will be used. For Documentation Team: Please document this option somewhere and the purpose of the same [ i.e. how repo deletion is affected by it ] Creating a new user permission rather than a setting might be better. While a setting would prevent all users from force deleting the repo, a permission would allow only the correct users to force delete the repo. The default would be the administrator. I feel like that would be better UX because a user who really wants to delete something will go and flip the setting if they have the power to. An idea that Justin mentioned that might help would be an extra checkbox in the UI on the warning modal that pops up. The user would need to check it to confirm that they're serious about deleting the repo. That plus a new user permission would make this new feature pretty safe I think. (In reply to Ian Ballou from comment #5) > An idea that Justin mentioned that might help would be an extra checkbox in > the UI on the warning modal that pops up. The user would need to check it > to confirm that they're serious about deleting the repo. That plus a new > user permission would make this new feature pretty safe I think. I am fine as long as we have a second layer of protection on top of the Bulk Deletion. But whatever we improve here, that also needs to be documented somewhere as it's a big behavioral change. I am happy to open a doc bz if that is needed. Created redmine issue https://projects.theforeman.org/issues/34576 from this bug Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34576 has been resolved. 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 (Moderate: Satellite 6.11 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:5498 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days |