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.
Bug 1287962 - Discovery does not warn if subnet does not have tftp proxy configured when provisioning a host
Summary: Discovery does not warn if subnet does not have tftp proxy configured when pr...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Discovery Plugin
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: Lukas Zapletal
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-03 07:18 UTC by Justin Sherrill
Modified: 2019-08-12 14:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-05-24 08:37:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 12705 0 None None None 2016-04-22 15:37:57 UTC

Description Justin Sherrill 2015-12-03 07:18:06 UTC
Description of problem:

When provisioning a host with discovery if the host's subnet does not have a tftp proxy configured the discovered host will reboot and go back into the discovery mode.  Foreman should be able to recognize this situation and at least warn the user that this is not configured.  

I'm not positive if there is even a use case for the tftp proxy to not be associated to the subnet in this sceanrio, so we may want to block the discovery provisioning attempt if not.

At least one customer has hit this.


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

How reproducible:
Always

Steps to Reproduce:
1.  Configure pxe discovery but do not associate the subnet with a tftp proxy/capsule
2. boot a system on that subnet
3. attempt to provision it

Actual results:
System reboots and goes back into discover

Expected results:
At least a warning is given to inform the user the tftp proxy is not configured on the subnet.


Additional info:

Comment 1 Bryan Kearney 2015-12-04 16:52:26 UTC
Created redmine issue http://projects.theforeman.org/issues/12705 from this bug

Comment 3 Lukas Zapletal 2015-12-07 09:32:01 UTC
Well, if you don't have TFTP set, no provisioning will be orchestrated. That has nothing to do with Discovery :-)

I am unlikely to give this a priority as plugins are not able to do stuff like UI warnings without Deface gem. But I could issue a Flash warning message during provisioning, this will only work with one host provisioning tho. If you can help me reviewing and testing the patch, let me know.

Comment 4 Bryan Kearney 2016-02-29 17:11:34 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/12705 has been closed

Comment 5 Lukas Zapletal 2016-03-01 15:01:02 UTC
Upstream bug was mis-closed.

Comment 6 Lukas Zapletal 2017-05-24 08:37:14 UTC
Guys, this is trivial thing that does not need to be tracked here, we have an upstream issue, I am unlikely to work on that soon.


Note You need to log in before you can comment on or make changes to this bug.