Hi Everyone,
I just thought i'd get this information out to the userbase about an
issue that we encountered yesterday with the smart proxy and Sinatra
1.3.2.
When using Smart-proxy with Sinatra 1.3.2 we found that when a DHCP
reservation was attempted when creating a new host for provisioning it
was failing with a 400 error (Foreman 0.4.0) or "No Subnet detected
for: <Subnet><Subnet>" (Foreman 0.4.1 or later).
<Subnet> in this case is the subnet value incorrectly repeated twice.
An error message similar to the below was also found in the debug
logs for the proxy:
E, [2012-01-10T12:11:29.503146 #20052] ERROR – : No Subnet detected
for: "10.21.9.010.21.9.0"
With Ohads help, this has been tracked down as an issue with Sinatra
1.3.2 and a downgrade to the 1.3.1 gem allowed us to proceed.
I don't know why but I hited this bug today.
Just for information, the gem sinatra 1.3.5 seems to fix the problem. @Keiran : thx for the initial mail which allow me to fix the problem really
quickly !
Romain
···
2012/1/12 Keiran
Hi Everyone,
I just thought i’d get this information out to the userbase about an
issue that we encountered yesterday with the smart proxy and Sinatra
1.3.2.
When using Smart-proxy with Sinatra 1.3.2 we found that when a DHCP
reservation was attempted when creating a new host for provisioning it
was failing with a 400 error (Foreman 0.4.0) or "No Subnet detected
for: " (Foreman 0.4.1 or later).
in this case is the subnet value incorrectly repeated twice.
An error message similar to the below was also found in the debug
logs for the proxy:
E, [2012-01-10T12:11:29.503146 #20052] ERROR – : No Subnet detected
for: “10.21.9.010.21.9.0”
With Ohads help, this has been tracked down as an issue with Sinatra
1.3.2 and a downgrade to the 1.3.1 gem allowed us to proceed.
