Description of problem: Failed to delete the subscriptions from UI. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Login Satellite through UI. 2. Go to the Content sidebar and select Subscriptions 3. Click on manage manifest file 4. Upload Manifest file form local system, manifest file uploaded successfully. 5. Select Subscriptions and click on the delete button. 6. go to Monitor sidebar and select the task, In the task, we get the errors like "Unit 9fc0ab19-9de9-45a2-97e4-402e953b6ef9 has been deleted Unit 9fc0ab19-9de9-45a2-97e4-402e953b6ef9 has been deleted" Actual results: Subscriptions failed to delete. Expected results: Subscriptions should be deleted. Additional info:
Created redmine issue https://projects.theforeman.org/issues/27056 from this bug
Created redmine issue https://projects.theforeman.org/issues/27062 from this bug
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27062 has been resolved.
Thanks John for clarifying the below statement. One correction in mine statement(Comment #9 in steps 4th line it was actually subscription not manifest) "I wanted to remove the subscription from Satellite, So I selected the subscription and click on Delete button but it was failed to remove and get a message like "The Subscription Allocation providing the imported manifest has been removed. Please create a new Subscription Allocation and import the new manifest." that was actually correct if we are uploading the non-existent manifest file." The above error is expected because the subscriptions are no longer valid for that manifest.
This bug has been successfully verified in 6.6.0 Snap14.
Verified point: * Manifest file successfully deleted. * Selected subscription successfully deleted and get a proper message. * Get a proper error message if we delete a subscription of a non-existent manifest file.
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/RHSA-2019:3172