Project

General

Profile

Bug #32921

DHCP next-server option is "false" when tftp-servername was not provided

Added by Lukas Zapletal over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
Lukas Zapletal
Category:
TFTP
Target version:
2.5.2
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/8635
Fixed in Releases:
2.5.2, 3.0.0
Found in Releases:
Red Hat JIRA:

Description

When installer option --foreman-proxy-tftp-servername is unset, smart proxy DHCP module renders next-server as "false". This is caused by expecting serverName is returned as nil, however, it looks like smart proxy can return empty string too.

Associated revisions

Revision 32181a11 (diff)
Added by Lukas Zapletal over 1 year ago

Fixes #32921 - treat empty TFTP servername correctly

History

#1 Updated by Lukas Zapletal over 1 year ago

  • Triaged changed from No to Yes
  • Target version set to 2.5.2

Requesting backport to 2.5 and 2.4

#2 Updated by Lukas Zapletal over 1 year ago

  • Category changed from TFTP to TFTP
  • Project changed from Smart Proxy to Foreman

#3 Updated by The Foreman Bot over 1 year ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/8635 added

#4 Updated by The Foreman Bot over 1 year ago

  • Fixed in Releases 3.0.0 added

#5 Updated by Tomer Brisker over 1 year ago

  • Fixed in Releases 2.5.2 added

#6 Updated by Lukas Zapletal over 1 year ago

  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF