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 - Content | Assignee: | Jeremy Lenz <jlenz> |
| Status: | ON_QA --- | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | high | Docs Contact: | Adam Lazik <alazik> |
| Priority: | high | ||
| Version: | 6.10.3 | CC: | addubey, ahumbe, ajambhul, alazik, aruzicka, bangelic, dhjoshi, inecas, jlenz, jpasqual, jwfrey, kgaikwad, kstokes, momran, pcreech, pdudley, rlavi, sadas, saydas, tasander, wpinheir |
| Target Milestone: | 6.14.0 | Keywords: | PrioBumpGSS, Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | rubygem-katello-4.9.0.12-1 | Doc Type: | Known Issue |
| Doc Text: |
.Information from host group is not completely inherited when provisioning a discovered host in the Satellite web UI
When you provision a discovered host, after selecting a host group and trying to customize the host entry, many critical pieces of information are missing. This results in a failed deployment attempt.
As a workaround, perform one of the following actions:
* Provision the host using hammer:
[literal]
----
# hammer discovery provision --name discovered_host_name \
--hostgroup-id your_hostgroup_id \
--organization-id your_organization_id \
--location-id your_location_id \
--new-name new_host_name\
--build true
----
For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/hammer_cli_guide/reference#hammer-discovery-provision[hammer discovery provision] in `Hammer CLI Guide`.
* Configure discovery rules and enable auto-provisioning so that no manual intervention is required to provision a discovered host.
For more information, see link:https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/provisioning_hosts/index#Creating_Discovery_Rules_provisioning[Creating Discovery Rules] in `Provisioning Hosts`.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 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
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 ] 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. Connecting redmine issue https://projects.theforeman.org/issues/36608 from this bug *** Bug 2056696 has been marked as a duplicate of this bug. *** *** Bug 2226991 has been marked as a duplicate of this bug. *** Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/36608 has been resolved. |