1. Proposed title of this feature request Rather than just showing "Repository cannot be deleted since it has already been included in a published Content View" , include the name of CV and versions where the repository included. 2. What is the nature and description of the request? Change in code for the product is required to achieve the desired goal. 3. Why does the customer need this? (List the business requirements here) This will allow spending less time in finding out the name of CV's and versions. 4. How would the customer like to achieve this? (List the functional requirements here) Right now, if I try to disable a repository that is part of a Content View, It will only show following message. ~~ Repository cannot be deleted since it has already been included in a published Content View. Please delete all Content View versions containing this repository before attempting to delete it. ~~ When customer will have many CV's and is not aware of which CV they need to look into , they will open up a support case and we will eventually suggest executing the second rake command present in https://access.redhat.com/solutions/3180551 , to get the list of affected CV's and their versions where the repository is included. If the same can be already printed as a part of the Pop-up message in UI, that makes the work for the customer much easier . 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. - Sync some RH repos - Add those repos in a CV, publish a new version of the same and promote the same. - Now try to disable any of those repos from Content --> Red Hat Repositories page and It should print the CV name and version where the repo is included. 6. Is there already an existing RFE upstream or in Red Hat Bugzilla? No. 7. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)? As soon as possible 8. Is the sales team involved in this request and do they have any additional input? No. 9. List any affected packages or components. - tfm-rubygem-katello 10. Would the customer be able to assist in testing this functionality if implemented? NA 11. Additional information: NA
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33710 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