Activity
From 10/20/2015 to 11/18/2015
11/18/2015
-
08:37 AM Feature #4917: Smart-Proxy Realm Provider for Active Directory
- Oh hi, sorry I missed this. This is great, thanks!
The best way to get comments would to get a PR open.
My per...
11/16/2015
-
01:13 PM Bug #12466 (Ready For Testing): Parsing subnets for ISC DHCP fails
-
04:42 AM Bug #12466: Parsing subnets for ISC DHCP fails
- Brandon, can you please apply the patch bellow:...
-
10:01 AM Bug #12469 (Closed): ISC DHCP proxy errors when attempting to delete nonexistant records
- Applied in changeset commit:f24be74d8f51f44aa8730769d2e468683804254c.
-
09:03 AM Bug #12469: ISC DHCP proxy errors when attempting to delete nonexistant records
- Leaving on .1 so we've got more time to soak test this change. The regression (#12465) needs to go in sooner as it'l...
-
- Removing from the 1.10.0 blockers as it seems to stem entirely from the linked bug, where a deleted entry is still be...
-
- Raise Proxy::DHCP::InvalidRecord if delRecord is called on a nonexistant record by looking for the `omshell` error.
11/13/2015
-
-
- Note that Foreman deliberately ignores a 404 HTTP response from the smart proxy during DHCP record deletion, expectin...
-
- When trying to delete an nonexistent host via omshell the ISC DHCP proxy an exception is raised and an error returned...
-
- Sorry I should have been more clear, it no longer find any subnets.
Nightly:
> D, [2015-11-13T04:39:25.710406 #10... -
- Parsing fail to retrieve subnet infos or just print warnings in logs ?
-
- https://github.com/theforeman/smart-proxy/commit/e2a21ecff6cf153890e93ad7c28a932396ae02d8#diff-79ebe89624de84cfd48356...
-
-
- Looks like a regression to me, the parse_config_and_leases_for_records method shouldn't be performing a subnet lookup...
-
- In /var/lib/dhcpd/dhcpd.leases the following type of entry may appear:
> host test.example.com {
> dynamic;
> de...
11/12/2015
-
08:02 AM
Feature #12211 (Closed): Improve DHCP subnets parsing to get more informations from DHCP server
- Applied in changeset commit:e2a21ecff6cf153890e93ad7c28a932396ae02d8.
- 07:40 AM Revision e2a21ecf: Fixes #12211 - Improve DHCP subnets parsing to get more informations from DHCP server
-
- Applied in changeset commit:839ca954a620b8496d6ea9e5c992684c70ef34ee.
-
- Mario Gamboa wrote:
> the variables :tsig_keytab, :tsig_principal is not pass the value into the /usr/share/forema... -
06:38 AM Bug #12449: Keytab not configured via dns_tsig_keytab for DNS GSS-TSIG support
- Hi the patch was already apply but still issues now with the kerberos apparently on /usr/share/foreman-proxy/modules/...
-
-
-
- Thanks for the report. This looks like a bug that we're not setting up the keytab location from the settings correct...
-
- from proxy.log in debug mode
D, [2015-11-12T19:48:10.770624 #25828] DEBUG -- : /usr/share/foreman-proxy/modules/dns_... -
- i upgrade foreman from 1.9.3 to 1.10 and now i can't register the record of the new vms into the active directory
... -
11/11/2015
-
09:01 AM
Bug #12136 (Closed): foreman-proxy fails to start if ruby-rgen is missing
- Applied in changeset commit:7cbe47ab867a9a844885d164553faf09603507be.
- 08:37 AM Revision 7cbe47ab: Fixes #12136: load only Puppet dependencies that are required by the config
- in puppet_proxy only dependencies and concrete implementation classes that
are required by the configuration are bein... -
04:45 AM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- There's probably stuff I've missed, but our workaround is to add this into dhcp_conflict_detected? :
return false ...
11/10/2015
-
05:01 PM Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- Hi Folks ,
do you think this is possible to workaround, mittigate somehow?
VM -
11:01 AM
Bug #12254 (Closed): Pin addressable for Ruby 1.8 compatibility
- Applied in changeset commit:248751937b99947a00c5d21a47f2527327b263da.
- 10:55 AM Revision 24875193: Fixes #12254: pinned addressable gem to ~> 2.3.8
- This is the last version to support 1.8.7.
-
09:01 AM
Bug #12138 (Closed): Failure to run smart-proxy from another package that has it as a dependency
- Applied in changeset commit:c9f0a075c6bb7e63ae56c44c2614e9cb233782e2.
-
- 08:11 AM Revision c9f0a075: Fixes #12138: Add require statements to run from bundler
- Adding these allows smart_proxy to be run from bundler.
-
05:01 AM
Bug #8946 (Closed): Exception thrown when foreman-proxy restarts with SIGTERM
- Applied in changeset commit:616d41a7841009a632e65f0b6360bdeec58df260.
- 04:36 AM Revision 616d41a7: Fixes #8946: Added a handler for SIGTERM
11/09/2015
-
11:09 AM
Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- I think it's the other way around -- fact import is the case that needs "special" treatment. I don't think you can tr...
-
- Can you give me an idea of what patch you might accept here ? I personally don't believe that the current behaviour w...
-
07:01 AM
Feature #12370 (Closed): Provide TTIN trap for stacktrace log output
- Applied in changeset commit:2c40ea555caf00d96874b712a8c44c2fdb6adb25.
- 06:39 AM Revision 2c40ea55: Fixes #12370 - proxy logs stacktrace on SIGTTIN
11/07/2015
-
10:07 PM Bug #12359: 100% cpu usage foreman-proxy after upgrade to 1.9
- And this is the log from the original installation (from which ticket was created).
Ubuntu 14.04
foreman-proxy 1.10... -
- This is the log form different foreman-proxy
Ubuntu 14.04
foreman-proxy 1.9.2-1...
11/05/2015
-
08:07 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)
- I see. Well, I think it is to always a good idea to ping an IP to be suggested to make sure it is not live on the net...
-
05:54 PM
Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)
- I need to find an ip that might be useable first. The choices I have atm is parsing the lease file or pinging the who...
-
- What will prevent you from using OMAPI instead of parsing the whole lease file to make sure the IP is not given away?...
-
05:17 PM
Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)
- Yeah, I was thinking I can use omapi for all calls except 'unused_ip' one, which will require parsing of the lease fi...
-
- Great! One thing though - if you read through my notes from 2 years ago, parsing a lease file is *not* the only probl...
-
03:46 PM
Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)
- It's an improvement, albeit a small one. The biggest improvement will come when we stop parsing the lease file on eve...
-
- Dmitri, do the changes from http://projects.theforeman.org/issues/11866 help here at all? Or are they even supposed to?
-
01:12 PM
Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- It's possible to manually assign an ip address to an interface during host creation. It's also possible that ip sugge...
-
- OK, this code is completely new to me so bound to be things I was missing. Presumably you could make dhcp_update_requ...
-
12:21 PM
Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- Keep in mind this is also used during host creation, for which it makes sense. I think your change breaks host creati...
-
- I may well be being dense, but why would you want to check this unless you know it's changed ? I can't think of a sce...
-
08:13 AM
Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- Look on the foreman side. I think the calls to smart-proxy are being triggered here, when save! is being called: http...
-
- I've had a poke around in the code but it's not obvious where that might be happening. Can you give me a steer where ...
-
09:14 AM Refactor #12402 (New): Configure proxy with syslog by default
- Smart proxy already have new SYSLOG setting which logs via syslog socket instead of a file. The only limitation is th...
11/04/2015
-
10:43 AM
Bug #2687 (New): Performance issues with large ISC dataset (DHCP smart proxy)
-
- And as you know I also just raised an issue about importing network interfaces ;)
-
- That would explain a lot if that is the case. We've been trying to debug puppet timeouts for weeks now, and have been...
-
- Matt Jarvis wrote:
> Anecdotally it did seem like the DHCP records are being validated during puppet runs for some r... -
- In case it's useful, here's the dump using latest github code :
Starting thread dump for current Ruby process
===... -
- Yes, I've got DEBUG logging turned on at the minute.
-
- Anecdotally it did seem like the DHCP records are being validated during puppet runs for some reason - is this the ca...
-
- We have around 150 hosts, split across two environments with different proxies.
-
- Our lease file is around 3MB, and the environment is currently completely static so there shouldn't be any add_record...
-
10:09 AM
Bug #12392: 100% cpu usage on foreman-proxy DHCP calls
- Smart-proxy is responding to three simultaneous calls to add a dhcp record, which is an expensive operation (and woul...
-
- So it's DHCP-related, since Foreman's calling @/dhcp/:network/:record@ there. I have been suspecting that Foreman mi...
-
- Starting thread dump for current Ruby process
=============================================
Thread TID-11812860
... -
- Here you go, this is the same patch designed for 1.9 - changing smart_proxy.rb instead:
https://github.com/thefore... -
- launcher.rb only exists in latest smart-proxy code - can I patch the trap code in somewhere else in 1.9.2 ?
-
- We don't have any smart proxy plugins installed. I'll try the debugging step.
-
- Could you check the comment on #12359 and try the same debugging step that Lukas suggests there? It will help us nar...
-
- At least since 1.8, the cpu usage on the foreman-proxy has been increasing massively. We now see it using 100% of cpu...
-
- https://github.com/theforeman/smart-proxy/compare/theforeman:1.9-stable...domcleal:1.9-stable-ttin.patch - equivalent...
-
09:23 AM Refactor #12394 (Resolved): Netsh Deprecated in Windows 2012R2
- When installing the Foreman Smart-Proxy for DHCP on a Windows 2012R2 host there is a deprecation warning that netsh w...
11/02/2015
-
-
- The same way we do this for Foreman Core.
-
- Are you able to acquire stacktrace? Proxy does not provide signal trap, but if you modify launcher.rb with this code:...
-
05:01 AM
Bug #12319 (Closed): Proxy templates API breaks on concurrent requests
- Applied in changeset commit:26aba8520d3d32ca27b9708cb98169bc31d43d7b.
- 04:16 AM Revision 26aba852: Fixes #12319: fixed race condition in templates module
- Multiple simultaneous requests to /unattended/template_type no longer fail.
10/31/2015
-
- after upgrade from 1.8 to 1.9 at some point the ruby process of foreman-proxy starts consuming high amounts of mem an...
10/29/2015
-
12:11 PM Bug #2687: Performance issues with large ISC dataset (DHCP smart proxy)
- I realize this is an old ticket but figured I would start here. We are seeing much higher load on our dhcp server / ...
10/28/2015
-
-
-
10/27/2015
-
- After some time I see also:...
-
- Here is one from latest development environment proxy running on Ruby 2.0:...
-
06:41 AM
Bug #12319: Proxy templates API breaks on concurrent requests
- I assume this is under 1.8.7? Can you attach the backtrace?
-
- When trying to render templates concurrently, multiple (different) failures occurs.
Reproducer:... -
- Yes, NFS I think. Lukas wrote up some documentation on the foreman-dev list, but it hasn't been submitted as part of...
10/26/2015
-
- While this is certainly a useful thing to have, how does one go about the fact that *.conf files from ISC DHCP are ex...
-
- Assuming this is Foreman 1.7, please try again with 1.10.0-RC1, the startup code has been refactored since. I can't ...
10/23/2015
-
11:14 AM Bug #12295 (Closed): Smart proxy stops listening on HTTPS port after log rotate
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1273785
Description of problem:
The foreman-proxy stops l... -
- That looks like it's still there then, thanks for confirming. I'd guess it's also happening during service stop (on ...
-
10:38 AM Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM
- After rebooting my foreman vm, I then get the following error messages:...
-
- I don't think that's related, it's a completely different process reporting an error - it's the Puppet agent, not the...
-
- Ok I just built a new foreman 1.10.0 on Centos 7.1. ...
10/22/2015
-
- Refactoring ticket without any description, PR has no description. All we have is one comment which mostly explains i...
-
- addressable 2.4.0 is scheduled to drop Ruby 1.8.7 support, so it should be pinned to < 2.4. addressable is a test de...
10/20/2015
-
- It looks like the handler originally came from #11098, which is also a 1.10.0 change. The thing is that both handler...
-
09:45 AM
Bug #8946: Exception thrown when foreman-proxy restarts with SIGTERM
- change introduced in 335a1610 (https://github.com/theforeman/smart-proxy/commit/335a1610fae8cd74720e2d9841d904deb8ff1...
-
10:02 AM
Bug #12217 (Closed): `ruby_21` is not a valid platform` with older versions of Bundler
- Applied in changeset commit:00875b34eafe4993a7b0bcd93f7b238f86858b76.
-
-
- Using :platforms in a Gemfile with newer Ruby versions is incompatible with older Bundler versions that we use on a n...
- 09:37 AM Revision 00875b34: Fixes #12217: support older versions of bundler
- No longer rely on :platforms to install test-unit dependency
-
08:09 AM
Feature #12209: Introduce support for dependency injection in dns module
- Also used in puppet_proxy (one of the examples: https://github.com/theforeman/smart-proxy/blob/develop/modules/puppet...
-
- Ohad Levy wrote:
> whats the usage case? could you elaborate?
https://github.com/theforeman/smart_proxy_dns_power... -
- Pull request: https://github.com/theforeman/smart-proxy/pull/330
-
-
05:23 AM
Bug #10581: UTF8 encoding error on realm update with freeipa
- Probably should document the locale/character encoding we expect.
-
03:35 AM Bug #10581: UTF8 encoding error on realm update with freeipa
- I've encountered the same error several times with puppet, the cause was my system's locale wasn't set properly and d...
Also available in: Atom