Activity
From 07/11/2016 to 08/09/2016
08/09/2016
- 12:02 PM Bug #15985 (Closed): Pxegrub2 config file prefix missing
- Applied in changeset commit:d4b60b36842ce5203cc009863ef89e21d71176b5.
- 11:34 AM Revision d4b60b36: fixes #15985 - Pxegrub2 tftp filename prefix
- 06:22 AM Bug #16021 (Closed): inotify queue overflow halts ISC lease file monitoring
- When using ISC lease file monitoring (nightly), the inotify event queue can overflow with many events if they're not ...
- 05:32 AM Bug #6022: puppetssh fails due to host key prompt when trying to do puppetrun
- Hi,
Fix for version 1.12.1 :...
08/08/2016
- 04:53 PM Feature #16009: Support for native iPXE
- Please ignore PR #450 - it is already closed on github.
- 04:39 PM Feature #16009 (Ready For Testing): Support for native iPXE
- 04:38 PM Feature #16009 (Closed): Support for native iPXE
- Add native iPXE support in smart-proxy as per thread https://groups.google.com/forum/#!searchin/foreman-users/ipxe$20...
- 12:10 PM Bug #10581: UTF8 encoding error on realm update with freeipa
- Also, I expect this issue is with ruby 1.9+, right?
- 11:58 AM Bug #10581: UTF8 encoding error on realm update with freeipa
- We have seen similar issue in remote execution, the problem was we were not indicating properly that the
external st... - 09:08 AM Feature #2482 (New): Global search in DHCP reservations/leases using MAC and/or hostname
- https://github.com/theforeman/smart-proxy/pull/97 was opened, but is now closed due to inactivity.
- 06:20 AM Feature #13326 (New): Update list of features in Foreman on Smart Proxy startup
- The pull request has been closed due to inactivity.
- 03:05 AM Bug #14911: Racing for free IPs resulting in DHCP reservation conflicts
- The smart proxy is meant to retain a lock on the IP for a period to prevent it being reallocated.
08/04/2016
- 03:19 PM Bug #15985 (Ready For Testing): Pxegrub2 config file prefix missing
- 03:15 PM Bug #15985 (Closed): Pxegrub2 config file prefix missing
- #12633 added Pxegrub2 pxe variant, grub2 expects a client's MAC address prefixed by 01- as the config file format. th...
- 02:06 PM Bug #14911: Racing for free IPs resulting in DHCP reservation conflicts
- I have poked at this a bit more and it's not DHCP only. If I retry DHCP I can also get
fatal: [localhost]: FAILE... - 06:02 AM Bug #15959 (Closed): Remove recursive require from lib/proxy/log_buffer/decorator
- Applied in changeset commit:37fb340ae11e4992aac8d49e276773235d7550df.
- 06:00 AM Revision 37fb340a: Fixes #15959 - removed recursive require
- 05:09 AM Revision 05b96b99: Fixes #15944 - Make it obvious that messages come from DHCP
- The occasional log reader might not know if this refers to a DNS or
DHCP 'record'.
Capitalize DHCP consistently.
08/03/2016
- 10:27 AM Bug #15959 (Ready For Testing): Remove recursive require from lib/proxy/log_buffer/decorator
- 10:25 AM Bug #15959 (Closed): Remove recursive require from lib/proxy/log_buffer/decorator
- 07:30 AM Refactor #15942 (Ready For Testing): Update dns providers to use new module initialization and configuration
08/02/2016
- 10:32 AM Refactor #15942 (Closed): Update dns providers to use new module initialization and configuration
07/29/2016
- 11:02 AM Refactor #15864 (Closed): Pxelinux kind as an alias for Syslinux
- Applied in changeset commit:056e0c49d85ef8832490bdc118a5431fff71ca5a.
- 10:06 AM Revision 056e0c49: Fixes #15864 - Pxelinux alias variant for Syslinux
- 07:02 AM Bug #2687 (Closed): Performance issues with large ISC dataset (DHCP smart proxy)
- Applied in changeset commit:7bd71b5efd38b609f5acf80bf3b5c899b3bd7e1c.
- 06:42 AM Bug #1090 (Feedback): When editing DHCP records, ISC backend times out if the number of subnets is large.
- The inotify-related changes from ticket #2687 have now been made in develop (nightly) for 1.13, which should drastica...
- 06:41 AM Bug #12359 (Feedback): 100% cpu usage foreman-proxy after upgrade to 1.9
- The inotify-related changes from ticket #2687 have now been made in develop (nightly) for 1.13, which should drastica...
- 06:41 AM Bug #12392 (Feedback): 100% cpu usage on foreman-proxy DHCP calls
- The inotify-related changes have now been made in develop (nightly) for 1.13, which should drastically reduce the amo...
- 06:28 AM Revision 7bd71b5e: Fixes #2687: Leases file is no longer parsed on every request
- Also: refs 12392, #12359, #12425, #1090
- 06:01 AM Bug #15865 (Closed): Pin json_pure to < 2.0.0 for Ruby < 2.0.0
- Applied in changeset commit:5a38c119eed6f2a7a161d300aff4d16bafa86ab9.
- 05:36 AM Revision 5a38c119: Fixes #15865 - pin json_pure to < 2.0.0 for RUBY_VERSION < 2.0.0
07/28/2016
- 07:53 AM Feature #15874: Log X-Request-ID by default
- Make sure this gets recorded in structured format in logger buffer as well, so we can easily pull out logs (e.g. erro...
- 05:41 AM Feature #15874 (Closed): Log X-Request-ID by default
- The default log configuration of the smart proxy should log the contents of the X-Request-ID header if it's set, whic...
- 07:51 AM Feature #15877 (Duplicate): Print session/request id in foreman-proxy logs
- Ticket #15874.
- 07:49 AM Feature #15877 (Duplicate): Print session/request id in foreman-proxy logs
- After Foreman is able to pass session/request as HTTP headers, we should send them to logs similarly Foreman core do ...
07/27/2016
- 11:57 AM Bug #15865 (Ready For Testing): Pin json_pure to < 2.0.0 for Ruby < 2.0.0
- 11:55 AM Bug #15865 (Closed): Pin json_pure to < 2.0.0 for Ruby < 2.0.0
- json_pure >= 2.0.0 isn't supported on earlier rubies, which leads to test failures.
- 11:08 AM Refactor #15864 (Ready For Testing): Pxelinux kind as an alias for Syslinux
- 11:06 AM Refactor #15864 (Closed): Pxelinux kind as an alias for Syslinux
- We are removing template variant attribute from OS in Foreman Core and template kind will define what to pass to Prox...
- 07:08 AM Feature #15853 (Rejected): Add tests for Infoblox DNS provider
- 06:58 AM Feature #15853 (Rejected): Add tests for Infoblox DNS provider
07/26/2016
- 11:42 AM Bug #15790 (Rejected): In MS DHCP provider disabling ddns should be done on subnet scope, not per record.
- 11:42 AM Bug #15790: In MS DHCP provider disabling ddns should be done on subnet scope, not per record.
- You are right, I followed the docs which turned out to be lacking/misleading. Thanks for the correction!
- 09:49 AM Bug #15790 (Feedback): In MS DHCP provider disabling ddns should be done on subnet scope, not per record.
- Why do you say this? Which version of the DHCP server are you using. I admit that I have only used W2K8 DHCP and high...
07/25/2016
- 06:02 AM Bug #15791 (Closed): Intermittent DHCPServerMicrosoftTest failures on ruby 1.8.7
- Applied in changeset commit:bce15a5de363f6ba41476e4b66ae4d680d50bfe9.
- 04:43 AM Bug #15791: Intermittent DHCPServerMicrosoftTest failures on ruby 1.8.7
- ...
- 05:00 AM Revision bce15a5d: Fixes #15791 - no more intermittent test failures in ms dhcp test
07/22/2016
- 02:08 PM Bug #15800 (New): Disable the module when one or more providers it relies on haven't been configured
- Might be helpful to suggest how to resolve the configuration issue too.
- 10:00 AM Bug #15791 (Ready For Testing): Intermittent DHCPServerMicrosoftTest failures on ruby 1.8.7
- 09:53 AM Bug #15791 (Closed): Intermittent DHCPServerMicrosoftTest failures on ruby 1.8.7
- Due to non-deterministic order of hash key iteration when assigning values to dhcp options.
- 08:04 AM Bug #15790 (Rejected): In MS DHCP provider disabling ddns should be done on subnet scope, not per record.
- Disabling of ddns per record isn't supported.
- 08:03 AM Bug #15789 (Resolved): In MS DHCP provider general/Vendor options must exist before assigning values to them
- Or the reservation will end up in an inconsistent state (some/all options may be missing).
07/21/2016
- 06:02 AM Bug #13575 (Closed): Don't fail due to missing PXEClient DHCP opt on 2008R2
- Applied in changeset commit:e5aa23440a5042f5697788e354c62a5be826ab30.
- 05:38 AM Revision e5aa2344: fixes #13575 - Don't fail on missing PXEClient dhcp opt
- Due to #2870 the dhcp_native_ms provider always tries to set the
PXEClient opt to empty. However this does not exist ... - 03:02 AM Support #15760 (Feedback): Foreman 1.12.0. puppetrun not working after upgrading from foreman 1.11.2.to 1.12.0
- It looks like an error from the smart proxy, possibly that the Puppet component failed to start and/or upgrade correc...
07/20/2016
- 08:30 PM Support #15760: Foreman 1.12.0. puppetrun not working after upgrading from foreman 1.11.2.to 1.12.0
- [root@ol07fmn00 ~]# puppet --version
3.8.7 - 08:29 PM Support #15760 (Resolved): Foreman 1.12.0. puppetrun not working after upgrading from foreman 1.11.2.to 1.12.0
Hello,
I updated foreman from version from 1.11.2 to 1.12.0. Puppetrun is not workin aftet upgrade. it was w...
07/18/2016
- 02:46 AM Feature #2736: implement a Wake On Lan function/button
- +1
Because the Clients could be in different Networks, the Admin should be able to add WoL Proxies for specific Ho...
07/14/2016
- 07:16 PM Bug #14719: Allow TLSv1 for compatibility with some clients.
- That would be my guess as to what is happening CentOS 5 was not tested as part of this change and even early versions...
- 07:11 PM Bug #14719: Allow TLSv1 for compatibility with some clients.
- > I believe this indicates that foreman itself is trying to establish a connection with an older protocol.
correct... - 06:47 PM Bug #14719: Allow TLSv1 for compatibility with some clients.
- Having a similar issue communicating between foreman and a smart-proxy after an upgrade to 1.12 and debian8.
Forem...
07/12/2016
- 06:00 AM Bug #10678: Foreman-proxy throws [RestClient::NotAcceptable]: 406 Not Acceptable upon server restart
- Anything in puppet logs by any chance?
- 05:10 AM Bug #10678: Foreman-proxy throws [RestClient::NotAcceptable]: 406 Not Acceptable upon server restart
- Confirm on 1.11.1
Also available in: Atom