Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When disabling Red Hat repositories on Satellite, Katello will try to remove the product altogether if the given repository is the last member of its respective product to be enabled on Satellite.
If the product is in a sync plan, Katello will also try to remove the product from the sync plan.
However, if the sync plan contains also other products that are no longer on Satellite, then an error message pops up while disabling the repository, stating it failed to _add_ a product to Satellite. It's really confusing.
Version-Release number of selected component (if applicable):
satellite-6.10.2-1.el7sat.noarch
foreman-2.5.2.18-3.el7sat.noarch
katello-4.1.1-3.el7sat.noarch
How reproducible:
100% of the time given the preconditions are met.
Steps to Reproduce:
1. Have a Satellite with multiple Red Hat products enabled and a sync plan including all those products.
2. Disable all repos of one of those products but cause some failure to remove the product from the sync plan.
3. Disable all repos of another one of those products.
Actual results:
When disabling the last repo of the second product -- which would cause an update to the sync plan -- an error will pop up saying something like:
Validation failed: Can not add product Red Hat Enterprise Linux Server - Extended Life Cycle Support because it is disabled.
...and the ForemanTasks task enters paused-error state.
Expected results:
If an error is happening due to a sync plan operation, the pop up message should specify that the issue is happening at that level, not the "disable repository" level.
I'd also say the repository should _not_ fail to be disabled from Satellite if its respective product can be removed from the sync plan. Maybe the action could finish with a Stopped-Warning state/result instead of ending in Paused-Error.
Additional info:
The fact that the error message says it failed because it was unable to _add_ a _product_ when we're trying to _disable_ a _repository_. This is absolutely confusing.
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 (Important: Satellite 6.15.0 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-2024:2010