Activity
From 08/27/2012 to 09/25/2012
09/17/2012
- 09:21 AM Feature #1458: HTTP/HTTPS/FTP Proxy-Support
- I have the same problem here with Compute Resource API support.
I would like to be able to define HTTP proxy for EC2 ...
09/14/2012
- 07:54 AM Feature #1856 (Closed): allow the proxy to run under rack
- Applied in changeset commit:"200ce9017f67e7dac49338a21bebd36573d9210d".
09/12/2012
- 03:04 AM Revision 200ce901: fixes #1856 - adds a config.ru and allow the SP to run as a rack app.
- 03:03 AM Revision 07aedac4: added comment for code clarity
- 03:03 AM Revision 56947667: make sure that class parameters are prefixed correctly and not as strings
09/11/2012
- 08:19 AM Feature #1856: allow the proxy to run under rack
- see https://github.com/theforeman/smart-proxy/pull/33
- 07:31 AM Feature #1856 (Closed): allow the proxy to run under rack
- this should enable using it via passenger/thin etc.
it would also allow us to use it within rails itself as a mounte...
09/10/2012
- 09:36 AM Bug #1832: The subnet entry gets duplicated in "addRecord" creating a "No Subnet detected for 10.2.2.010.2.2.0" error
- this seems https://github.com/sinatra/sinatra/issues/452
09/05/2012
- 06:35 AM Bug #1836: Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts
- As is probably easy to surmise, downgrading Puppet to 2.7.18, at least on the Puppetmaster/Puppet CA server on which ...
- 03:40 AM Bug #1836 (Closed): Foreman chokes on "puppet cert clean host.does.not.exist.example.com" as of Puppet 2.7.19 and thus can't provision new hosts
- Applied in changeset commit:"a402c71290f2d8205e60b876f2a40dfa9fefacda".
- 03:33 AM Revision a402c712: fixes #1836 - puppet cert in 2.7.19 has a different exit code
08/30/2012
- 03:57 PM Bug #1761: confdir appears to be broken again in 1.0rc3
- From what I see a problem with the patch from #1552 is that it requires a confdir setting to be present in puppet.con...
- 09:40 AM Bug #1117: Permissions issue with RHEL package
- I think we discussed it with jmontleon and he already added foreman-proxy user to puppet group. I didn't check.
Good ...
08/29/2012
- 08:37 AM Bug #1833 (Duplicate): proxy met issue with puppet 2.7.19
- 08:08 AM Bug #1835 (Closed): foreman-proxy (:puppet: true) broken with puppet-2.7.19-1.el6
- Applied in changeset commit:"330dbef35376b88af4964b4d738c312486fbcdc0".
- 06:47 AM Revision 330dbef3: fixes #1835 - proxy now can import classes from puppet 2.7.19
08/28/2012
- 04:37 AM Bug #1806: puppet 2.6 depreciates puppetca
- I actually have a fix for this. Will send the pull request soon.
- 04:30 AM Feature #1829 (Closed): add bmc ipmi support to smart proxy
- fixed in commit:94cca053
- 04:28 AM Bug #1117 (Need more information): Permissions issue with RHEL package
- is still applicable with the latest 1.x packages?
- 04:26 AM Feature #1005 (Duplicate): Add support for fence-agents (remote power control)
- fixed in #1829
- 04:23 AM Revision ad37be47: Create the pid parent dir if it doesn't exist
- 04:19 AM Revision 94cca053: feature #1829 - add bmc ipmi support to smart proxy
08/27/2012
- 10:43 AM Bug #1835: foreman-proxy (:puppet: true) broken with puppet-2.7.19-1.el6
- I experienced the same issue when using puppet.noarch 0:2.7.19-1.el6 and puppet-server.noarch 0:2.7.19-1.el6. Here is...
Also available in: Atom