Project

General

Profile

Feature #25229

Foreman-Proxy for MSFT DHCP does not contain POST debug data

Added by Jeff Sparrow over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
DHCP
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Had some issues with DHCP lately so as I was digging through log files, I found out that the foreman-proxy logs for MSFT DHCP do not contain the debug output of POST.

Here is the deletion, with debug output:

D, [2018-10-01T08:03:34.277498 ] DEBUG -- : Rack::Handler::WEBrick is invoked.
D, [2018-10-01T08:03:34.281519 8ff5c54c] DEBUG -- : #<Proxy::DHCP::Reservation:0x000000051c1f88 @type="reservation", @name="rack399serv3.lab.beer.town", @subnet=#<Proxy::DHCP::Subnet:0x000000051c2960 @network="100.90.89.0", @netmask="255.255.255.0", @ipaddr=#<IPAddr: IPv4:100.90.89.0/255.255.255.0>, @options={}, @m=#<Monitor:0x000000051c2028 @mon_owner=nil, @mon_count=0, @mon_mutex=#<Thread::Mutex:0x000000051c1fd8>>>, @ip="100.90.89.50", @mac="24:6e:96:18:00:75", @options={:deleteable=>true, :hostname=>"rack399serv3.lab.beer.town", :nextServer=>"100.90.128.69", :filename=>"pxelinux.0", :PXEClient=>"", 81=>0}>
D, [2018-10-01T08:03:34.281519 8ff5c54c] DEBUG -- : Deleting 'rack399serv3.lab.beer.town (100.90.89.50 / 24:6e:96:18:00:75)'
I, [2018-10-01T08:03:34.286499 8ff5c54c]  INFO -- : 100.90.128.69 - - [01/Oct/2018:08:03:34 -0500] "DELETE /dhcp/100.90.89.0/mac/24:6e:96:18:00:75 HTTP/1.1" 200 - 0.0090

But then here is the POST of the DHCP entry, where we see no information at all about what it sent:

D, [2018-10-01T08:03:34.329518 ] DEBUG -- : Rack::Handler::WEBrick is invoked.
I, [2018-10-01T08:03:34.360499 8ff5c54c]  INFO -- : 100.90.128.69 - - [01/Oct/2018:08:03:34 -0500] "POST /dhcp/100.90.89.0 HTTP/1.1" 200 - 0.0310

Would be really helpful if we could see what information it was passing to DHCP.

History

#1 Updated by Lukas Zapletal over 2 years ago

  • Triaged changed from No to Yes
  • Tracker changed from Bug to Feature

Feel free to add this, it should be very easy. Please use the new trace call we have just made available in develop for this kind of noisy debug messages:

https://github.com/theforeman/smart-proxy/commit/9d4605334ad7fec1b2e344cba15f15567db9c00d#diff-8e0c75b46462891bf7fb5a906ab48db0R83

Also available in: Atom PDF