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.

Document URL: 

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/release_notes/?lb_target=preview

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/release_notes/index#known_issues

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/release_notes/index#ref_known-issues_assembly_introducing-red-hat-satellite

https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/release_notes/index#ref_known-issues_assembly_introducing-red-hat-satellite


Section Number and Name: 

"Known Issues"


Describe the issue: 

https://bugzilla.redhat.com/show_bug.cgi?id=2069324#c4 is one annoying bug that irritates both support engineers and end-users. 

Despite this being a known issue for over 4 releases of Satellite, We haven't documented it as one and that costs us additional time in the remote session with customers. 



Suggestions for improvement: 


I will like to have this BZ documented as a known issue with Satellite UI, for Satellite 6.10 - 6.13. 

I will also like to have the workaround mentioned there i.e. to 

Either use the hammer command i.e. 

# hammer discovery provision --name mac525400fea371 --hostgroup-id 1 --organization-id 1 --location-id 2 --new-name rhel79 --subnet-id 1 --pxe-loader 'iPXE Embedded' --build true

Or, Configure Discovery Rules so that, No manual intervention will be required. 

Provisioning guides "7.6. Creating Discovery Rules" section can be hyperlinked if needed. 


Additional information:

Hello,
preparing draft of the release note.

Hello Sayan,

Thank you for your quick response and collaboration!

I have created the PR and submitted for peer review:

https://gitlab.cee.redhat.com/satellite-6-documentation/docs-Red_Hat_Satellite_6/-/merge_requests/1660

The documentation has been updated. Look for "Information from host group is not completely inherited when provisioning a discovered host in the Satellite web UI" in the known issues:

https://dxp-docp-prod.apps.ext-waf.spoke.prod.us-west-2.aws.paas.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/release_notes/index?lb_target=preview#ref_known-issues_assembly_introducing-red-hat-satellite
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/release_notes/index#ref_known-issues_assembly_introducing-red-hat-satellite
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/release_notes/index#ref_known-issues_assembly_introducing-red-hat-satellite
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/release_notes/index#known_issues