Project

General

Profile

Actions
Copy link

Bug #30243

open

No Range check when creating a subnet in foreman UI

Added by Kal Aeolian over 4 years ago. Updated over 4 years ago.

Status:
New
Priority:
High
Assignee:
-
Category:
Network
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Foreman Maintain - 1.18.0
Red Hat JIRA:

Description

When creating a new subnet, there is no validation that a valid range has been entered, and no default range is automatically selected when empty.

This results in back code being pushed to the DHCP server, which results in the dhcpd server not starting, which results in servers all losing their IP addresses.

(and in the case of a short TTL, a production outage, as just happened to us.)

This is dangerous, DHCP range validation can cause the service to stop so this should be validated in both puppet and foreman UI code.

This occurs in at least Foreman v1.19.1.

Actions
Copy link
 #1

Updated by Kal Aeolian over 4 years ago

  • Priority changed from Normal to High

Also this was found in foreman 1.19 but I assume this happens in previous versions.

Actions
Copy link
 #2

Updated by Kavita Gaikwad over 4 years ago

  • Project changed from Foreman Maintain to Foreman
  • Category set to Network
Actions
Copy link

Also available in: Atom PDF