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.
DescriptionSebastian Hetze
2016-02-16 12:22:21 UTC
Description of problem:
When provisioning a system via images (templates) in a subnet with discovery feature enabled, the system is booted in discovery mode and the automatic provisioning fails.
Steps to Reproduce:
1. Enable discovery feature
2. Provision new host using an image (template)
Actual results:
new host boots into discovery mode
Expected results:
new host boots based on template and Kickstart Finish template is performed
Additional info:
when discovery feature is enabled, /var/lib/tftpboot/pxelinux.cfg/default is changed to boot into discovery mode by default.
Other than with provisioning from scratch, Foreman does not create individual tftp boot records for image based provisioning. That leads to this situation described above.
Given there has not been any other evidence of this being an issue with customers, neither has been reported in upstream, I'm closing this bug for now as WORKSFORME. Please repopen if the issue can be reproduced with the current satellite version.