Provisioning a host from Satellite server fails with `Disabling all modules in the group ['dhcp_isc', 'dhcp'] due to a failure in one of them: Unable to add subnet xxx.xxx.xxx.xxx/255.255.255.0`

Solution Verified - Updated

Environment

  • Red Hat Satellite 6.11.5.6-1
  • Red Hat Enterprise Linux 8.x

Issue

  • Provisioning a host from Satellite server fails with Disabling all modules in the group ['dhcp_isc', 'dhcp'] due to a failure in one of them: Unable to add subnet xxx.xxx.xxx.xxx/255.255.255.0

Resolution

  • Apply the steps in the Diagnostic Steps section of this KB solution.

  • Verify that the DHCP feature is listed in the Satellite's web UI under Infrastructue --> Capsules --> capsule.example.com --> Active features section, or alternatively via the following hammer command:

    # hammer capsule info --id capsule.example.com

    where capsule.example.com is the FQDN of either the integrated or an external capsule server.

  • If the DHCP feature is missing in the Satellite's web UI under Infrastructue --> Capsules --> capsule.example.com --> Active features section, click on the Refresh features button and verify whether the DHCP feature gets listed under the Active features section afterwards or not.

  • If the DHCP feature is still missing in the Satellite's web UI under Infrastructue --> Capsules --> capsule.example.com --> Active features section, run the followin command on the affected Satellite/Capsule server for which the DHCP feature is missing:

    # satellite-installer

  • Verify that, after running the satellite-installer command, the DHCP feature is now listed under the Active features section in the Satellite's web UI under Infrastructue --> Capsules --> capsule.example.com

For more KB articles/solutions related to Red Hat Satellite 6.x Provisioning Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Provisioning related Issues

Diagnostic Steps

  • Check in /var/log/foreman/production.log for errors similar to:

    2023-12-12T16:53:35 [I|app|df41f7a5] Adding Compute instance for client_host.example.com
2023-12-12T16:53:39 [W|app|df41f7a5] DHCP proxy does not report dhcp_filename_ipv4 or dhcp_filename_hostname capability. Foreman will pass boot server capsule.example.com as-is, the request might fail.
2023-12-12T16:53:39 [I|app|df41f7a5] Create DHCP reservation client_host.example.com for client_host.example.com-00:50:56:95:2f:c7/10.73.3.99
2023-12-12T16:53:39 [W|app|df41f7a5] Create DHCP Settings for client_host.example.com task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::NotFound]: 404 Not Found) for Capsule https://capsule.example.com:9090/dhcp
2023-12-12T16:53:39 [I|app|df41f7a5] Backtrace for 'Create DHCP Settings for client_host.example.com task failed with the following error: ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::NotFound]: 404 Not Found) for Capsule https://capsule.example.com:9090/dhcp' error (ProxyAPI::ProxyException): ERF12-6899 [ProxyAPI::ProxyException]: Unable to set DHCP entry ([RestClient::NotFound]: 404 Not Found) for Capsule https://capsule.example.com:9090/dhcp

  • Check in /var/log/foreman-proxy/proxy.log for errors like:

    2023-12-12T16:24:01  [E] Couldn't enable 'dhcp_isc'
2023-12-12T16:24:01  [E] Disabling all modules in the group ['dhcp_isc', 'dhcp'] due to a failure in one of them: Unable to add subnet xxx.xxx.xxx.xxx/255.255.255.0
SBR
Product(s)
Components
Category
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.