Created from redmine issue https://projects.theforeman.org/issues/11760

Upstream bug assigned to None

Would https://bugzilla.redhat.com/show_bug.cgi?id=2123932 not resolv the main concern here ?

That new feature for force deletion of a repo works very well whether It was included in CV or CCV ( and several versions of them ). So a user would not need to know where the repository is. If the goal is to delete the repo without needing to re-publish the CV or CCVs, this is the option to go for.


And in case the user wants to find out related CV or CCV versions, They can do it with this rake ( where 52 is the ID of the repo taken from "hammer repository list" command ):

# cat << EOF | foreman-rake console
conf.echo = false
Katello::Repository.find(52).clones.each { |repo| puts "Repo => #{repo.name} | CV => #{repo.content_view.name} | Version => #{repo.content_view_version.version} | Version_ID => #{repo.content_view_version.id} | Lifecycle => #{repo.content_view_version.environments.map(&:name).join(',')}"}  ; nil
EOF

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.

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/11760 has been resolved.

Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration.

Verified on Satellite Stream - version 51

Steps to Verify:
1) Create a Repository
2) Create a CV
3) Add the Repository to the CV, and publish the CV
4) Attempt to Delete the repository with `hammer repository delete --id=$REPO_ID`

Expected Results:
The Repository can't be deleted, and the message returned includes text mentioning the --remove-from-content-view-versions flag as a way to delete the Repository while also removing it from published CV Versions.
Running the command again with the --remove-from-content-view-versions true option successfully deletes the Repository

Actual Results:
The Repository can't be deleted, and the message returned includes text mentioning the --remove-from-content-view-versions flag as a way to delete the Repository while also removing it from published CV Versions.
Running the command again with the --remove-from-content-view-versions true option successfully deletes the Repository

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.