Bug 1832584 - Unable to delete repository - Content with ID could not be found
Summary: Unable to delete repository - Content with ID could not be found
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Management
Version: 6.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 6.7.1
Assignee: Jonathon Turel
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-06 20:49 UTC by Mike McCune
Modified: 2023-10-06 19:55 UTC (History)
1 user (show)

Fixed In Version: tfm-rubygem-katello-3.14.0.21-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1810250
Environment:
Last Closed: 2020-06-08 13:18:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 29316 0 Normal Closed Ignore missing candlepin content on product delete 2020-06-26 10:06:42 UTC
Red Hat Product Errata RHBA-2020:2422 0 None None None 2020-06-08 13:18:13 UTC

Comment 5 Lai 2020-05-18 15:56:54 UTC
Steps to retest:

1. Create a product
2. Create 2 custom repos and sync them
3. Content -> products -> <product_name>
4. Remove one custom repo created in step 2
5. Check task page
6. On CLI use hammer and run following command: hammer repository delete --id=<repo_id>

Expected result
step 5. Should show up as successfully delete repo and should show no errors.
Step 6. Running hammer repository list should not show deleted repo.

Actual:
step 5: Shows up as successfully deleted repo with no errors.
step 6: "Repository deleted" message shows up after deleting repo.  Deleted repo is not shown after running hammer list command.

Note: For step 6, I also checked on UI to see no errors showing up in task page.

Marking issue as verified in 6.7.1_01.

Comment 8 errata-xmlrpc 2020-06-08 13:18:03 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, 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/RHBA-2020:2422


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