Red Hat Bugzilla – Bug 1287962
Discovery does not warn if subnet does not have tftp proxy configured when provisioning a host
Last modified: 2017-05-24 04:37:14 EDT
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:
Created redmine issue http://projects.theforeman.org/issues/12705 from this bug
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.
Moving to POST since upstream bug http://projects.theforeman.org/issues/12705 has been closed
Upstream bug was mis-closed.
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.