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:
Error attempting to set the "Content Source" Capsule to a capsule that does not have the LifeCycle environment promoted to it.
"Failed to save: The selected content source and lifecycle environment do not match"
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.4
How reproducible:
Steps to Reproduce:
1. Create a Lifecycle Environment that does not have Content Promoted to it.
2. Set a Host group to use that Lifecycle Enviornment
3. Select a Content Source capsule from the dropdown that does not have that Lifecycle environment content synced.
Actual results:
Error: "Unable to save: The selected content source and lifecycle environment do not match"
Expected results:
Ability to set the content source as the capsule.
Additional info:
This worked prior to Satellite 6.4, and this new validation only appears to be for the hostgroup. An individual host can have the "Content Source" capsule set to a value that does not match the Lifecycle Environment, but a hostgroup cannot for some reason.
There was a workaround suggested in the support case of creating a Lifecycle Environment and assigning it to the capsule, but then never promoting anything to it.
This raised the question of the value of the validation. Is the extent of it just to verify the LE is valid for that capsule, and not that the actual content has been made available to the capsule?
Comment 13Tasos Papaioannou
2021-06-02 16:42:31 UTC
Verified on 6.10.0 snap 2.0.
Steps:
1. Add a Capsule server to the default organization's Library environment.
2. Create a new lifecycle environment.
3. Create a new host group, selecting the new lifecycle environment and the capsule server as the content source.
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 (Moderate: Satellite 6.10 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-2021:4702