Activity
From 12/01/2016 to 12/30/2016
12/29/2016
- 04:36 PM Refactor #17880 (Ready For Testing): DNS CNAME parameters methods are swapped
- 04:08 PM Refactor #17880 (Rejected): DNS CNAME parameters methods are swapped
- All DNS methods uses *fqdn* parameters as the target of the action and the second argument as the attribute that will...
- 03:44 PM Feature #17879 (Ready For Testing): Add DNS CNAME entry for nsupdate
- 03:36 PM Feature #17879 (Resolved): Add DNS CNAME entry for nsupdate
- DNS managed by Foreman should be able to assign aliases for hosts.
Smart-proxy API currently support DNS CNAME ent...
12/28/2016
- 08:27 PM Bug #17823: Non-JSON response from MS DNS record deletion
- This is one is covered by http://projects.theforeman.org/issues/17847.
The fixes are in place, here's the PR: https:... - 08:23 PM Bug #17847: MS DHCP Leases not being deleted
- Alex Brodov wrote:
> Dmitri Dolguikh wrote:
> > This isn't a bug but a feature: smart-proxy wasn't supposed to dele... - 05:44 PM Bug #17847: MS DHCP Leases not being deleted
- Dmitri Dolguikh wrote:
> This isn't a bug but a feature: smart-proxy wasn't supposed to delete lease records origina... - 07:55 AM Bug #17868 (Ready For Testing): dhcp option next-server ip not converted correctly
- 07:40 AM Bug #17868 (Closed): dhcp option next-server ip not converted correctly
- ISC file parser does not convert the next-server ip address correctly from "hex2ip" as method validate_ip is undefined.
- 04:26 AM Feature #17856: SmartProxy should support multiple dhcp reservations for the same ip address
- Dmitri Dolguikh wrote:
> There's a chance that it might be possible with ISC dhcpd when 'option dhcp-client-identifi... - 03:19 AM Feature #17856 (Ready For Testing): SmartProxy should support multiple dhcp reservations for the same ip address
12/27/2016
- 04:17 PM Bug #17847: MS DHCP Leases not being deleted
- This isn't a bug but a feature: smart-proxy wasn't supposed to delete lease records originally (and there's code ther...
- 03:22 PM Bug #17847: MS DHCP Leases not being deleted
- Dmitri Dolguikh wrote:
> This isn't an issue in smart-proxy version 1.14 and higher, and this partially duplicates h... - 02:30 PM Bug #17847 (Duplicate): MS DHCP Leases not being deleted
- This isn't an issue in smart-proxy version 1.14 and higher, and this partially duplicates http://projects.theforeman....
- 02:37 PM Bug #17862 (Rejected): Silence Sinatra/rack startup warning "TCPServer Error: Address already in use - bind(2)"
- This causes confusion about smart-proxy status.
- 02:34 PM Support #17707: after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- This is sinatra/rack issuing a warning on startup, please ignore it. Should a real conflict over a tcp port occur, sm...
- 11:51 AM Feature #17856: SmartProxy should support multiple dhcp reservations for the same ip address
- There's a chance that it might be possible with ISC dhcpd when 'option dhcp-client-identifier' is used to explicitly ...
- 08:45 AM Feature #17856 (Closed): SmartProxy should support multiple dhcp reservations for the same ip address
- Smart Proxy should support multiple dhcp records for the same ip address to support bonded interfaces. Cobbler alread...
12/26/2016
- 06:24 PM Support #17707: after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- I, [2016-12-27T00:10:20.762341 #2446] INFO -- : 192.168.85.32 - - [27/Dec/2016:00:10:20 +0100] "GET /puppet/ca HTTP/...
- 06:16 PM Support #17707: after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- i saw the same problem. CentOS 7.2 - 7.3
i will upload my proxy.log. - 10:20 AM Bug #17847 (Duplicate): MS DHCP Leases not being deleted
- When I'm deleting a host Foreman is sending a request to smart proxy to delete the reservation, but the lease will st...
12/25/2016
- 09:24 PM Bug #17823 (Ready For Testing): Non-JSON response from MS DNS record deletion
- 09:11 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Dmitri Dolguikh wrote:
> I should mention that 1.14 solves a few issues present in the original implementation of MS... - 08:19 PM Bug #17823: Non-JSON response from MS DNS record deletion
- I should mention that 1.14 solves a few issues present in the original implementation of MS dhcp interface, and if th...
- 08:15 PM Bug #17823: Non-JSON response from MS DNS record deletion
- > Is it going to be enough to use smart proxy 1.14?
I'm not sure what you mean.
You can try getting 1.13 to wor... - 07:55 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Dmitri Dolguikh wrote:
> I don't see any errors in the first log. The second attempt shows a failure to delete a hos... - 07:52 PM Bug #17823: Non-JSON response from MS DNS record deletion
- I don't see any errors in the first log. The second attempt shows a failure to delete a host with mac 00:50:56:8c:5f:...
- 07:33 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Dmitri Dolguikh wrote:
> Could you enable debug logging on the smart-proxy and post the log of the failing call here... - 07:01 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Could you enable debug logging on the smart-proxy and post the log of the failing call here?
- 06:21 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Dominic Cleal wrote:
> Which version of the smart proxy are you using? Please ensure it's also up to date, this look... - 12:46 PM Bug #17823: Non-JSON response from MS DNS record deletion
- Dominic Cleal wrote:
> Which version of the smart proxy are you using? Please ensure it's also up to date, this look... - 03:37 PM Feature #17843 (Ready For Testing): MS dnscmd interpreter won't be found
- 03:13 PM Feature #17843 (Closed): MS dnscmd interpreter won't be found
- The dns_nsupdate_main.rb can't work on Windows due to incompatible which usage.
Instead of using ...
12/22/2016
- 03:32 AM Bug #17823: Non-JSON response from MS DNS record deletion
- Which version of the smart proxy are you using? Please ensure it's also up to date, this looks a bit like it may have...
12/21/2016
- 07:38 PM Bug #17823 (Closed): Non-JSON response from MS DNS record deletion
- I'm using Foreman 1.13.2 and smart proxy with MS DHCP and MS DNS.
When I'm trying to delete the host for the first... - 08:01 AM Bug #14394 (Closed): WEBrick server version disclosure
- Applied in changeset commit:97dd5257a881028b2d9154dd634326793460dd33.
- 07:06 AM Revision 97dd5257: Fixes #14394 - Undisclose WEBrick server version
- 03:21 AM Support #17790 (Feedback): Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- dhcp.yml has enabled set to "http" (HTTP only), change it to either "https" or "true" to enable it on HTTPS as well a...
12/20/2016
- 11:47 AM Support #17790: Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- Alex Brodov wrote:
> Dominic Cleal wrote:
> > 1. Can you restart the smart proxy and include the whole log file? Th... - 11:46 AM Support #17790: Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- Dominic Cleal wrote:
> 1. Can you restart the smart proxy and include the whole log file? The startup may show that ... - 03:18 AM Support #17790: Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- 1. Can you restart the smart proxy and include the whole log file? The startup may show that the DHCP module failed t...
- 11:15 AM Bug #17800: ISC Dhcpd Config Parse Error
- Hmm.. it's unlikely I'm going to be in a position to update to EL7 anytime soon, removing the pool definition fixes t...
- 10:19 AM Bug #17800: ISC Dhcpd Config Parse Error
- The EL7 packages are only designed for EL7.
- 10:18 AM Bug #17800: ISC Dhcpd Config Parse Error
- Hm, doesn't look like anything past 12.4 is available for EL6 (what my systems are) so I guess I'm pooched till I do ...
- 10:10 AM Bug #17800 (Feedback): ISC Dhcpd Config Parse Error
- This file appears to parse since #16079, with the 10.30.0.0 subnet being registered. Can you please re-test on a newe...
- 09:59 AM Bug #17800 (Duplicate): ISC Dhcpd Config Parse Error
- After updating from Smart Proxy 9.x -> 12.4 the subnet in my dhcpd.conf was no longer being detected. I checked in on...
- 02:32 AM Bug #17783 (Duplicate): foreman-proxy exposes server version in header
- Duplicate of #14394
12/19/2016
- 07:20 PM Support #17790: Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- ...
- 06:40 PM Support #17790 (Resolved): Smart Proxy ERF12-2600 [ProxyAPI::ProxyException]: Unable to retrieve DHCP subnets ([RestClient::ResourceNotFound]: 404 Resource Not Found) for proxy
- Hi Team,
We're facing some issues with smart proxy, no hosts can be added due to this issue.
We have Foreman ru... - 06:05 PM Feature #17615: Introduce KEA DHCP provider for smart-proxy
- Some additional resources on KEA that Dmitri had asked me in the original thread:
> Kea has no management api what... - 04:09 PM Bug #17783 (Duplicate): foreman-proxy exposes server version in header
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1404867
Description of problem:
foreman-proxy sends ... - 01:30 PM Bug #17747 (Closed): Make foreman-debug aware of Puppet4
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1390929
Description of problem:
Puppet4 files live in d... - 03:21 AM Support #17707: after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- Can you provide the whole log file please (is this proxy.log)? Is it working correctly?
12/16/2016
- 05:01 AM Support #17707: after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- I forgot to say, the Server is running a CentOS7.
- 04:58 AM Support #17707 (Resolved): after Foreman-Installer: puppet TCPServer Error: Address already in use - bind(2)
- Good Morning together,
i installed a new Puppet Master Server (Puppet 4.8.1) with Foreman (1.13) over the foreman-...
12/13/2016
- 05:04 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
> This isn't enough information to diagnose the problem. Are incremental updates being used for move_to events to? ...
12/12/2016
- 11:01 AM Bug #17554 (Closed): ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- Applied in changeset commit:9445cae3964cf836c28074f700c8f8ba4792bf39.
- 10:04 AM Revision 9445cae3: Fixes #17554 - inotify events can't overflow the observer anymore
- 06:23 AM Bug #10678 (Need more information): Foreman-proxy throws [RestClient::NotAcceptable]: 406 Not Acceptable upon server restart
12/09/2016
- 09:41 AM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- > I noticed that after several hours of rsync'ing dhcpd.leases to 2nd and 3rd Foreman nodes, something gets a "lock" ...
- 08:55 AM Feature #17500 (Ready For Testing): Introduce providers for realm module
12/08/2016
- 05:31 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- Created http://projects.theforeman.org/issues/17615 for KEA DHCP provider feature.
Let's move all KEA-related conver... - 05:30 PM Feature #17615 (New): Introduce KEA DHCP provider for smart-proxy
- Introduce KEA DHCP provider for smart-proxy.
KEA is next-gen fast milti-node DHCP server by ISC. It uses DB backen... - 05:23 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- Dmitri Dolguikh wrote:
> You might be able to get syncd to work with smart-proxy, but this will require changes to s... - 02:16 AM Feature #4917 (Ready For Testing): Smart-Proxy Realm Provider for Active Directory
12/07/2016
- 08:01 AM Bug #17045 (Closed): Templates Smart Proxy API does not pass Hostgroup provisioning
- Applied in changeset commit:3b81b1d90378e23bc10f9100c6d8f243379894f0.
- 07:49 AM Revision 3b81b1d9: Fixes #17045 - hostgroup templates URLs proxied correctly
12/06/2016
12/05/2016
- 10:39 AM Bug #17566: TFTP provisioning fails when grub2 directory does not exist
- Was there any PXEGrub2 template associated with the host?
Can you share the proxy.log bit after you created the mi...
12/02/2016
- 08:43 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
> It is not what I've been talking about at all. I've been trying to point out that it is not possible to not drop ...- 04:34 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- > Well, if it is OK with Foreman developers and community to sacrifice the performance and scope of Foreman as produc...
- 01:38 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
> > So, if we step back and review the requirements for caching leases, what would that be? You mentioned keeping t...- 01:34 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
> > Well, yes, currently it is pretty much non-existent, but if it were, would you be interested in picking this up...- 12:30 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- > So, if we step back and review the requirements for caching leases, what would that be? You mentioned keeping track...
- 12:26 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- > Well, yes, currently it is pretty much non-existent, but if it were, would you be interested in picking this up as ...
- 12:24 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
> There is no way we can drop local state without reducing functionality/scope of smart proxy dhcp api.
Caching ...- 12:10 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
> Kea has no management api whatsoever (it's a step backwards compared to dhcpd in this regard), which makes it pre...- 04:05 AM Bug #17373: ISC dhcp provider is unable to handle very big networks
- > If the above approach (no-caching, on-demand queries only) make sense to you, I strongly believe it could be implem...
- 04:02 AM Bug #17373: ISC dhcp provider is unable to handle very big networks
- Kea has no management api whatsoever (it's a step backwards compared to dhcpd in this regard), which makes it pretty ...
- 02:39 PM Bug #17566 (Rejected): TFTP provisioning fails when grub2 directory does not exist
- After installation of the OS is complete the PXE boot configuration does not get switched to boot off the local disk....
- 04:41 AM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- You might be able to get syncd to work with smart-proxy, but this will require changes to syncd: on modify event it w...
- 04:22 AM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- > Meanwhile, I have a question for you, Dmitri - is it possible to handle :moved_to event the same way as :modify and...
12/01/2016
- 06:25 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- Well, to follow up on what I mentioned above - there's a difference in inotify events on a system that actually runs ...
- 05:59 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- Alas, I don't see any improvements in large deployment - as soon as inotify events start happening (i'm rsync'ing dhc...
- 02:17 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- I run ruby 2.0 included with CentOS 7:
ruby 2.0.0p598 (2014-11-13) [x86_64-linux]
I'll test your PR and let you... - 12:23 PM Bug #17554: ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- Konstantin, what ruby version are you using? I think the PR will resolve the problem you are seeing, but I couldn't v...
- 12:12 PM Bug #17554 (Ready For Testing): ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- 12:07 PM Bug #17554 (Closed): ISC dhcpd provider leases monitor doesn't keep up with lease file updates in a large network
- 02:58 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- > Konstantin, out of curiousity: I am working (#13806) on dnsmasq smart-proxy provider that will work fast. It's a sm...
- 12:19 PM Bug #17373: ISC dhcp provider is unable to handle very big networks
- I reopened the issue and also created a ticket dedicated to inotify watcher not being able to keep up with the events...
- 12:14 PM Bug #17373 (New): ISC dhcp provider is unable to handle very big networks
- 05:52 AM Bug #17373: ISC dhcp provider is unable to handle very big networks
- Konstantin, out of curiousity: I am working (#13806) on dnsmasq smart-proxy provider that will work fast. It's a smal...
- 12:39 PM Bug #17556 (Rejected): ISC dhcpd provider potentially discards leases too early or too late
- Time comparison on this line: https://github.com/theforeman/smart-proxy/blob/develop/modules/dhcp_isc/isc_state_chang...
Also available in: Atom