Bug #17506

smart-proxy Error while getting IP from AD DHCP (undefined method `key?')

Added by Kevin Carrasco over 1 year ago. Updated over 1 year ago.

Assigned To:Dmitri Dolguikh
Target version:Foreman - Team Ivan Iteration 6
Difficulty: Bugzilla link:
Found in release:1.13.2 Pull request:
Story points-
Velocity based estimate-
Release1.13.3Release relationshipAuto


After upgrading Foreman (CentOS 7) and Smart-Proxy (Windows) from 1.13.1 to 1.13.2 I'm getting the following error on the smart proxy while trying to acquire an unused IP address for a new host:

D, [2016-11-28T11:26:04.273136 #4984] DEBUG -- : undefined method `key?' for #<Proxy::MemoryStore:0x00000002a8da98 @root={}> (NoMethodError)

I've attached the smart-proxy.log in this ticket.

I also verified that the netsh command the proxy runs works properly when run from CMD:

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Windows\system32>c:\windows\system32\cmd.exe /c c:\Windows\System32\netsh.exe -c dhcp server show scope

 Scope Address  - Subnet Mask    - State        - Scope Name          -  Comment
==============================================================================     -  -Active        -W3rd VOIP VLAN 241   -W3rd VOIP, Cis     -  -Active        -W3rd DR              -West 3rd DR ro     -  -Active        -W3rd Servers VLAN 260-     -  -Active        -W3rd Workstations VLA-W3rd Workstati     -  -Active        -W3rd Technology VLAN -W3rd Technolog     -  -Active        -W3rd Corporate VLAN 2-Corporate work     -  -Active        -W3rd Renders VLAN 280-      -  -Active        -Studio Cloud Render n-Scalar Studio

 Total No. of Scopes = 8
Command completed successfully.

Let me know what other information will help resolve this issue. Thanks.

smart-proxy.log (6.43 KB) Kevin Carrasco, 11/28/2016 02:48 PM


#1 Updated by Michael Moll over 1 year ago

I guess this is related to #17387

#3 Updated by Kevin Carrasco over 1 year ago

  • Status changed from New to Resolved

Thanks guys, I've applied the change in your commit and that fixed the issue for me.

#4 Updated by Dmitri Dolguikh over 1 year ago

  • Status changed from Resolved to Closed

#5 Updated by Dominic Cleal over 1 year ago

  • Assigned To set to Dmitri Dolguikh
  • Release set to 1.13.3

#6 Updated by Ivan Necas over 1 year ago

  • Target version set to Team Ivan Iteration 6

Also available in: Atom PDF