Bug 2069324

Summary: No inheritance of CV and LCE while selecting host group for Discovered hosts.
Product: Red Hat Satellite Reporter: Avijit Roy <avroy>
Component: Hosts - ContentAssignee: Jeremy Lenz <jlenz>
Status: CLOSED ERRATA QA Contact: addubey
Severity: high Docs Contact: Adam Lazik <alazik>
Priority: high    
Version: 6.10.3CC: addubey, ahumbe, ajambhul, alazik, aruzicka, bangelic, dhjoshi, inecas, jlenz, jpasqual, jwfrey, kgaikwad, kstokes, momran, osousa, pcreech, pdudley, rlavi, sadas, saydas, tasander, wpinheir
Target Milestone: 6.14.0Keywords: PrioBumpGSS, Triaged, UserExperience
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: rubygem-katello-4.9.0.12-1 Doc Type: Bug Fix
Doc Text:
.Host group information inheritance when provisioning a discovered host Previously, when you provisioned a discovered host, the content view and lifecycle environment information was missing after selecting a host group and trying to customize the host entry. This resulted in a failed deployment attempt. With this release, information from the host group is correctly inherited when you provision a discovered host.
Story Points: ---
Clone Of:
: 2242917 (view as bug list) Environment:
Last Closed: 2023-11-08 14:17:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Avijit Roy 2022-03-28 17:56:54 UTC
Description of problem:

Host group is not populating many information while we select host group from :

Hosts >> Discoverd Hosts >> Click on Provision >> Select Host group >> Customize Host


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

6.10
6.11


How reproducible:

1. Create a normal HG (not nested) with all information. 

2. Discover the host. 

3. Go to Hosts >> Discoverd Hosts >> Click on Provision >> Select Host group >> Customize Host


Actual results:

Many fields like Lifecycle Environment, Content View will be empty. CV and LCE are always blank

Expected results:

All fields should be populated with the exact information mentioned in the Host Group. 


Additional info:

1. This does not happen if we do auto-provisioning. 
2. This does not happen if we Click on create host instead of Customize Host.
3. In case we do not select the HG in the first place and just do Customize Host and then select the HG, it populates all information.

Comment 4 Sayan Das 2022-08-25 09:43:23 UTC
Raising the severity to high as this is impacting most of the Foreman-Discovery customers who don't use Discovery Rules and relies on manual customization of host after discovering the same.

We need to ensure that following while this is being fixed:

** Hosts >> Discovered Hosts >> Click on Provision >> Select Host group >> Customize Host and here the CV+LCE should be properly selected along with the content source and the Media should be auto-selected as well based on how the Hostgroup is configured. 

** After successful customization and submission, The UI of Satellite should not become a blank page. It should really submit the host and come back to the page where it shows the info about the Submitted host for the build. and the Host should be rebooted for build as well. 

   [ This has been reported by some users as well ]

Comment 5 Sayan Das 2022-08-25 11:14:31 UTC
FYI workaround for both of the problems 

A) Use Auto Provisioning to deploy the system via the discovery rule

B) Use a hammer to provision the discovery host e.g. 

# hammer discovery provision --hostgroup-id 2 --organization-id 1 --location-id 2 --build true --name mac5254009f9e0d --new-name myrhel


If we use GUI, we will either end up with blank CV + LCE , or even if we workaround that, then as soon as we submit the host, we will see blank page and the host is not exactly submitted for build.

Comment 17 Jeremy Lenz 2023-07-20 18:10:59 UTC
Connecting redmine issue https://projects.theforeman.org/issues/36608 from this bug

Comment 18 Paul Dudley 2023-07-28 20:51:13 UTC
*** Bug 2056696 has been marked as a duplicate of this bug. ***

Comment 19 Leos Stejskal 2023-08-01 07:00:45 UTC
*** Bug 2226991 has been marked as a duplicate of this bug. ***

Comment 20 Bryan Kearney 2023-08-02 04:02:01 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36608 has been resolved.

Comment 33 errata-xmlrpc 2023-11-08 14:17:47 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 (Important: Satellite 6.14 security and bug fix update), 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-2023:6818