Activity
From 11/26/2013 to 12/25/2013
12/19/2013
-
03:13 PM Bug #3918: Password option is not effective in database.yaml
- To confirm this, list postgresql processes. In this case, I have running instance of Foreman:
postgres 2298 ... -
- Reported by Cristian Falcas - thanks.
-
It looks like the pg adapter in Rails uses UNIX sockets, which we
configure to trust when ident is set properly....
12/12/2013
-
09:53 AM Feature #3476: As a User, I would like to install foreman in a HA mode
- I think that one part of having foreman HA would be to just have the foreman HA. That excludes all proxy related item...
12/11/2013
-
02:02 PM
Bug #3851: Reports with errors on the puppet master side are not shown as failed
- ah, right... if the case of the non-cached catalog I also have the error "err Puppet Could not retrieve catalog; sk...
-
01:53 PM Bug #3851: Reports with errors on the puppet master side are not shown as failed
- The difference between daemon and --test mode might be "usecacheonfailure" which is enabled by default I think and di...
-
01:45 PM
Bug #3851: Reports with errors on the puppet master side are not shown as failed
- The host has a green zero and "No changes", so it's not set into error state...
I recall that it worked with Puppet ... -
- Is this the same as #2976 do you think? Does the host show the error, but the report metrics don't?
-
10:30 AM
Bug #3851 (Closed): Reports with errors on the puppet master side are not shown as failed
- If a puppet agent gets an error like "Could not retrieve catalog from remote server: Error 400 on SERVER: Failed to p...
-
- Description of problem:
Foreman only creates reverse zone file for first set of prefixes in a multi-prefixed subnet....
12/03/2013
-
05:52 PM
Refactor #3640 (Closed): Rakefy this package
- Applied in changeset commit:721a83ae2f2dde2dc7ab0fe892b6ffb7a211e8f0.
Also available in: Atom