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.
This can be easily workarounded by pressing Control+L to clear and refresh screen. If this does not work for you, you can add "quiet" or "loglevel=0" kernel command line option before booting the image (in Grub press "E" and append this). If this works for you, you can use discovery-remaster script to add this option to ISO so you don't need to do this everytime.
I am making necessary change so this is fixed in future and no option will be needed.
TRIAGE NOTES:
Satellite 6.3 candidate
QA NOTES:
After PXE-less boot, sign in onto the image and verify:
[lzap@box ~]$ sysctl kernel.printk
kernel.printk = 0 4 1 7
That the first column is zero so kernel will not print any messages on tty.
Comment 4Satellite Program
2017-10-27 12:01:31 UTC
VERIFIED
Version tested:
Satellite 6.3 snap 33
# rpm -q foreman-discovery-image
foreman-discovery-image-3.4.3-1.el7sat.noarch
No standard log output blocking during discovery provisioning.
Comment 11Satellite Program
2018-02-21 16:54:17 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, 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-2018:0336