Project

General

Profile

Actions

Bug #12705

open

Issue warning when TFTP is not set on the Subnet

Added by Bryan Kearney over 9 years ago. Updated about 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Discovery plugin
Difficulty:
trivial
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1287962
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:


Related issues 1 (0 open1 closed)

Is duplicate of Discovery - Bug #9563: Provision should not be allowed when subnet doesn't have proxies set upDuplicate02/26/2015Actions
Actions

Also available in: Atom PDF