Project

General

Profile

Actions

Bug #15240

closed

Couldn't enable plugin dhcp: Parameter 'subnets' is expected to have a non-empty value

Added by Martin Dobrev almost 8 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
Fixed in Releases:
Found in Releases:

Description

Hi,

after upgrading my smart proxy nodes to 1.11.2 and theforeman-foreman_proxy to 2.5.0 I can't use DHCP any more. I'm getting an error on the SP nodes that subnets can't be a non-empty array but I can't really set this parameter via the module. As far as I can see this parameter is introduced in the master branch of the Puppet module.

proxy.log

E, [2016-05-31T12:46:39.160714 #23759] ERROR -- : Couldn't enable plugin dhcp: Parameter 'subnets' is expected to have a non-empty value
E, [2016-05-31T12:47:58.615590 #23904] ERROR -- : Couldn't enable plugin dhcp: Parameter 'subnets' is expected to have a non-empty value

dhcp.yaml

---
# Enable DHCP management
# Can be true, false, or http/https to enable just one of the protocols
:enabled: https

# valid providers:
#   - dhcp_isc (ISC dhcp server)
#   - dhcp_native_ms (Microsoft native implementation)
#   - dhcp_virsh (simple implementation for libvirt)
:use_provider: dhcp_isc
:server: 127.0.0.1
# subnets restricts the subnets queried to a subset, to reduce the query time.
#:subnets: [192.168.205.0/255.255.255.128, 192.168.205.128/255.255.255.128]


Related issues 2 (0 open2 closed)

Related to Smart Proxy - Bug #15143: DHCP :subnet: parameter no longer optionalDuplicate05/23/2016Actions
Related to Smart Proxy - Bug #14952: dhcp_isc not respecting the :subnets: settings anymoreClosed05/06/2016Actions
Actions

Also available in: Atom PDF