Activity
From 11/30/2017 to 12/29/2017
12/29/2017
- 06:04 PM Bug #22098 (Closed): bundle install fails on Ruby <2.2
- ...
- 11:30 AM Feature #4917 (Ready For Testing): Smart-Proxy Realm Provider for Active Directory
- 10:35 AM Feature #4917 (New): Smart-Proxy Realm Provider for Active Directory
- PR was closed.
12/18/2017
- 09:45 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- Okay. So here's what I did then in conf.d/auth.conf for the rules 'puppetlabs environments' and 'puppetlabs environme...
- 08:08 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- > I don't think this is a good idea?
I don't see why not, tbh. Authentication over http isn't useful (I'd argue it... - 08:06 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- If I use allow-unauthenticated I don't authenticate the rest of my hosts anymore. This setting is a boolean, not a wh...
- 05:32 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- I was thinking about`allow-unauthenticated`: https://puppet.com/docs/puppetserver/5.1/config_file_auth.html#allow-all...
- 04:52 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- Thank you Dmitri. Dropping authentication, could you please be a bit more specific? Are we then talking about 'client...
- 02:01 PM Bug #21975 (Closed): DHCP filename option is ignored
- Applied in changeset commit:13a7c60f097bcfb10d7bc1790739add652a4f169.
- 01:50 PM Revision 13a7c60f: Fixes #21975 - filename dhcp option is accepted now
12/17/2017
- 10:22 AM Feature #15535 (Closed): Log http ports used by modules during startup
- 10:20 AM Revision 2fc0ec8c: Fixes #15535 - http ports used by plugins are being logged now.
12/16/2017
- 10:11 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- I think you can drop authentication for smart-proxy addresses on puppet master -- http headers over http aren't provi...
- 10:03 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- Maybe this is something I do not understand. Suppose I have one apache load balancer where my agents connect to. This...
- 03:18 AM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- I think this is actually fine, see
https://github.com/theforeman/puppet-puppet/issues/429
https://github.com/thefor...
12/14/2017
- 08:04 PM Bug #21975 (Ready For Testing): DHCP filename option is ignored
- 12:21 PM Bug #21975: DHCP filename option is ignored
- Regression in develop/1.17. This is working on 1.15 and 1.16.
- 12:20 PM Bug #21975 (Closed): DHCP filename option is ignored
- When new DHCP entry is created, filename option is no longer honored and completely ignored.
curl -#k --cert $... - 01:08 PM Bug #21463: proxy detects existing dhcp record as conflict
- This patch created a regression #21975 I spent some time on it, found the line which caused it but I don't understand...
12/12/2017
- 01:32 PM Support #21876: foreman-proxy unable to access puppet api when allow-header-cert-info = true
- Marking as 1.16.1 to study including a fix for this for that version
12/10/2017
- 04:36 AM Support #21917: ERF12-2357 [ProxyAPI::ProxyException]: Unable to set DNS entry ([RestClient::BadRequest]: 400 Bad Request)
- Make sure that dns zones and views are configured correctly. I would also suggest to execute nsupdate manually to mak...
- 04:26 AM Support #21917 (Resolved): ERF12-2357 [ProxyAPI::ProxyException]: Unable to set DNS entry ([RestClient::BadRequest]: 400 Bad Request)
- when creating a host i get an error with the dns on the smart proxy .. katello 3.5 and foreman 1.16
D, [2017-12-10...
12/06/2017
- 02:58 AM Support #21876 (Resolved): foreman-proxy unable to access puppet api when allow-header-cert-info = true
- while installing a new installation for experimental purposes before our upgrade to Puppet 5 & Foreman 1.16, I'm foun...
12/04/2017
- 09:01 PM Support #21236 (Closed): No ping check causes duplicated IP with MS DHCP
- Applied in changeset commit:ba7eceeff7b2e19c306097288a30ae2a49918450.
- 08:30 PM Revision ba7eceef: Fixes #21236 - No ping check causes duplicated IP with MS DHCP
Also available in: Atom