Project

General

Profile

Actions

Bug #9011

closed

Satellite 6.0 manifest cannot be refreshed after updating entitlements

Added by Partha Aji almost 10 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
High
Assignee:
Category:
-
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1183114
Description of problem:

Satellite 6.0 manifest cannot be refreshed after updating entitlements

Version-Release number of selected component (if applicable): Satellite 6.0

How reproducible: Customer Satellite 6.0 is currently broken and issue is %100 repeatable

Steps to Reproduce:
1. Add entitlements to manifest via the Red Hat Customer Portal
2. From the Satellite GUI attempt to 'Refresh Manifest'

Actual results:
The manifest is not refreshed and an error message indicating it has failed is printed in the GUI.

Expected results:
The new manifest will be updated to reflect the recent changes made in the Red Hat Customer Portal to the manifest.

Additional info:

There are errors logged in '/var/log/foreman/production.log' when the 'Refresh Manifest' button is clicked in the Satellite GUI. The main error that caught my attention is:

DeleteRestrictionError: Cannot delete record because of dependent repositories

Full sosreport and foreman-debug are attached to the SFDC case that will be attached to this bug.


Related issues 2 (0 open2 closed)

Related to Katello - Refactor #9012: The manifest actions in dynflow ought to rely on other actions for deleting repos and products, etcRejectedActions
Related to Katello - Feature #9054: In the UI, provide indication of (and maybe a way to remove) orphaned Red Hat products (via dynflow)RejectedActions
Actions

Also available in: Atom PDF