Activity
From 10/22/2012 to 11/20/2012
11/20/2012
- 11:52 AM Revision 81894ba3 (installer): Throw error when YAML type is unknown
- 11:30 AM Revision 5d3df572 (puppet-foreman): Fix Debian paths for Puppet3
- 08:31 AM Bug #1956 (Resolved): dhcp module: fails to setup static leases
- Merged in ef1ba611e, thanks for the patch.
11/19/2012
- 02:25 PM Revision ef1ba611 (puppet-puppet): Merge pull request #17 from sgzijl/1708-add_missing-sitepp
- Create site.pp even if empty
- 12:40 PM Revision 91a59f77 (puppet-puppet): Update manifests/server/config.pp
- Reference bug tickets puppet and foreman.
Don't replace existing a site.pp - 10:24 AM Revision 708ce7a6 (puppet-foreman): Remove use of $osfamily as not all OSes support it
11/18/2012
- 04:50 AM Revision d77c5376 (puppet-dhcp): #1956 fix_dhcp_module-static_leases
- 04:48 AM Bug #1956: dhcp module: fails to setup static leases
- Fix: replace 'concat::fragment' to 'concat_fragment' in dhcp/manifests/host.pp:14
- 04:47 AM Bug #1956 (Resolved): dhcp module: fails to setup static leases
- The DHCP module fails to setup static leases when using 'dhcp::host'...
11/15/2012
- 03:22 PM Bug #1507 (Closed): Documnetation / integration with puppet / webrick stuff
- docs updated
- 02:32 PM Revision 6a34f1bc (puppet-puppet): fixes #1708 create site.pp even if empty
- 12:37 PM Bug #1226 (Closed): puppet 2.7.* break installation of foreman-proxy
- This doesn't seem to be an issue any longer with the versions of the modules included with the latest installer so I'...
- 09:31 AM Bug #1226: puppet 2.7.* break installation of foreman-proxy
- can't reproduce with latest foreman installer
11/12/2012
- 09:28 AM Revision 54e03426 (puppet-puppet): Only use `puppet cert` on Puppet 3 systems, since Foreman searches for
- puppetca first
11/09/2012
- 10:20 AM Revision c1a1f64e (puppet-tftp): Fix TFTP location on newer RHEL/Fedora releases
- 07:01 AM Revision a402e188 (installer): Change YAML path to /etc/foreman-proxy/answers.yaml for consistency
- Parameterise foreman_installer class for answers.yaml location
11/07/2012
- 03:03 PM Revision 3a931109 (puppet-foreman_proxy): Fixes #1928 - Start proxy service at boot, init script supports status
- 12:29 PM Revision e53770fb (puppet-foreman_proxy): fixes #1928 - start proxy service at boot, init script supports status
- 12:26 PM Revision c7abb26e (puppet-foreman_proxy): Use version-specific puppetca command from puppet pull 15
- 11:11 AM Bug #1928 (Resolved): foreman-proxy not configured to start at boot (enable)
- Merged: https://github.com/theforeman/puppet-foreman_proxy/pull/27
- 07:25 AM Bug #1928 (Resolved): foreman-proxy not configured to start at boot (enable)
- The foreman-proxy service (in puppet-foreman_proxy) is only configured with @ensure => running@ and not @enable => tr...
- 10:26 AM Revision 37ad6182 (installer): Update foreman, foreman_proxy, and puppet module commits
11/01/2012
- 05:44 PM Revision c417fb59 (puppet-foreman_proxy): Remove a debug notify
- This notify will mark the server as active every run and adds little value.
- 10:06 AM Revision 78c0ec5a (puppet-foreman): Puppet 2.6 compatibility
- Puppet 2.6 doesn't allow a trailing comma after the last argument.
10/25/2012
- 10:40 AM Revision 64e7c7d2 (installer): Reapply YAML in develop branch
- 10:39 AM Revision eb4cc43c (installer): Revert "Installation via a yaml file." - moving this to a develop branch
- This reverts commit 84a9a25f7ea7b74a3b11c3959c09bb247ad1f1e4.
10/24/2012
- 09:45 AM Revision 4264a4d4 (puppet-puppet): Correctly determine the puppet command on old and new puppet systems
- (Credit to Bill ONeill <woneill@pobox.com> for the initial work)
10/23/2012
- 10:16 AM Revision 3efd15f3 (installer): foreman: bugfix bump
- 10:15 AM Revision 176b2144 (puppet-foreman): Fix typo in component name and don't default to nightly
- 09:57 AM Revision 4dae9342 (installer): foreman/proxy: version bump
- 09:45 AM Revision aae145e1 (puppet-foreman_proxy): Don't use nightly by default
- 09:42 AM Revision 45b62b76 (puppet-foreman): Use new debian repo, remove unused param
- 02:36 AM Support #1912 (Resolved): production database is not configured
- I did saw foreman-0.1.6-2.noarch in your logs, that version is about 2 years old now :), have a look at yum.theforema...
10/22/2012
- 03:54 PM Support #1912: production database is not configured
- Thanks a lot! Greg... I didn't have idea of that... it works now...
- 03:43 PM Support #1912: production database is not configured
- If that database.yml is literal, then your whitespace is wrong - in YAML whitespace does matter. Try a 2 space indent...
- 03:40 PM Support #1912 (Resolved): production database is not configured
- Hello,
I am new installing and configuring Foreman. My installation includes puppetmaster, passenger, RabbitMQ & MCo...
Also available in: Atom