Bug 1656127 - Unable to set HostGroup content source to capsule that isn't synced
Summary: Unable to set HostGroup content source to capsule that isn't synced
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Host Group
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: 6.10.0
Assignee: Ian Ballou
QA Contact: Tasos Papaioannou
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-12-04 18:41 UTC by Dylan Gross
Modified: 2022-04-18 12:20 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:08:27 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32100 0 Normal New Unable to set HostGroup content source to capsule that isn't synced 2021-03-15 18:22:18 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:08:40 UTC

Description Dylan Gross 2018-12-04 18:41:41 UTC 
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.
Comment 5 Dylan Gross 2018-12-04 18:56:21 UTC 
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 11 Ian Ballou 2021-03-15 18:22:17 UTC 
Created redmine issue https://projects.theforeman.org/issues/32100 from this bug
Comment 12 Bryan Kearney 2021-03-23 16:06:19 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32100 has been resolved.
Comment 13 Tasos 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.
Comment 16 errata-xmlrpc 2021-11-16 14:08:27 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 (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
Note You need to log in before you can comment on or make changes to this bug.