Project

General

Profile

Actions

Bug #26277

closed

Foreman provides DHCP address via smart-proxy and used by server but No actual DHCP lease was created.

Added by Olmo Rupert almost 6 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

During provisioning of a virtual machine.

Foreman requests DHCP from the smart-proxy and does "return" / use an IP address from the designated subnet.

But it turned out that the actual lease was not created.

This is the log from the smart-proxy

logs:

proxy.log:

2019-03-07T14:53:32 3bcfd74e [I] Started GET /serverName
2019-03-07T14:53:32 3bcfd74e [I] Finished GET /serverName with 200 (0.4 ms)
2019-03-07T14:53:32 3bcfd74e [I] Started GET /172.21.99.0/mac/00:50:56:8e:95:bc
2019-03-07T14:53:32 3bcfd74e [E] No DHCP record for MAC 172.21.99.0/00:50:56:8e:95:bc found
2019-03-07T14:53:32 3bcfd74e [I] Finished GET /172.21.99.0/mac/00:50:56:8e:95:bc with 404 (1.14 ms)
2019-03-07T14:53:32 3bcfd74e [I] Started GET /172.21.99.0/ip/172.21.99.30
2019-03-07T14:53:32 3bcfd74e [E] No DHCP records for IP 172.21.99.0/172.21.99.30 found
2019-03-07T14:53:32 3bcfd74e [I] Finished GET /172.21.99.0/ip/172.21.99.30 with 404 (1.02 ms)

messages

Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:14:53:32 CET] "GET /tftp/serverName HTTP/1.1" 200 28
Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: - -> /tftp/serverName
Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:14:53:32 CET] "GET /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc HTTP/1.1" 404 58
Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc
Mar  7 14:53:32 pr-infra-deploy101 dhcpd: DHCPDISCOVER from f8:f2:1e:46:6d:b0 via ens224: network 172.21.99.0/24: no free leases
Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:14:53:32 CET] "GET /dhcp/172.21.99.0/ip/172.21.99.30 HTTP/1.1" 404 53
Mar  7 14:53:32 pr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0/ip/172.21.99.30

later after verifying there was no actual lease i asked foreman for a new ip address in the same subnet.
after this op it succesfully created the dhcp lease entry.

again the logs:
proxy.log:

2019-03-07T17:02:15 3bcfd74e [I] Started GET /serverName
2019-03-07T17:02:15 3bcfd74e [I] Finished GET /serverName with 200 (0.52 ms)
2019-03-07T17:02:15 3bcfd74e [I] Started GET /172.21.99.0/mac/00:50:56:8e:95:bc
2019-03-07T17:02:15 3bcfd74e [E] No DHCP record for MAC 172.21.99.0/00:50:56:8e:95:bc found
2019-03-07T17:02:15 3bcfd74e [I] Finished GET /172.21.99.0/mac/00:50:56:8e:95:bc with 404 (1.09 ms)
2019-03-07T17:02:15 3bcfd74e [I] Started GET /172.21.99.0/ip/172.21.99.37
2019-03-07T17:02:15 3bcfd74e [E] No DHCP records for IP 172.21.99.0/172.21.99.37 found
2019-03-07T17:02:15 3bcfd74e [I] Finished GET /172.21.99.0/ip/172.21.99.37 with 404 (0.96 ms)
2019-03-07T17:02:15 3bcfd74e [I] Started GET /serverName
2019-03-07T17:02:15 3bcfd74e [I] Finished GET /serverName with 200 (0.34 ms)
2019-03-07T17:02:15 3bcfd74e [I] Started DELETE /172.21.99.0/mac/00:50:56:8e:95:bc
2019-03-07T17:02:15 3bcfd74e [I] Finished DELETE /172.21.99.0/mac/00:50:56:8e:95:bc with 200 (0.38 ms)
2019-03-07T17:02:16 3bcfd74e [I] Started POST /172.21.99.0
2019-03-07T17:02:16 3bcfd74e [I] Finished POST /172.21.99.0 with 200 (58.56 ms)

messages:

Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:15 CET] "GET /tftp/serverName HTTP/1.1" 200 28
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: - -> /tftp/serverName
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:15 CET] "GET /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc HTTP/1.1" 404 58
Mar  7 17:02:15 [36mpr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:15 CET] "GET /dhcp/172.21.99.0/ip/172.21.99.37 HTTP/1.1" 404 53
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0/ip/172.21.99.37
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:15 CET] "GET /tftp/serverName HTTP/1.1" 200 28
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: - -> /tftp/serverName
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:15 CET] "DELETE /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc HTTP/1.1" 200 0
Mar  7 17:02:15 pr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0/mac/00:50:56:8e:95:bc
Mar  7 17:02:16 pr-infra-deploy101 smart-proxy: pr-infra-foreman101.df1.my.net - - [07/Mar/2019:17:02:16 CET] "POST /dhcp/172.21.99.0 HTTP/1.1" 200 0
Mar  7 17:02:16 pr-infra-deploy101 smart-proxy: - -> /dhcp/172.21.99.0

Actions

Also available in: Atom PDF