Bug #1790
closedForeman Installer
Description
running :
export MODULE_PATH="/etc/puppet/modules/common" mkdir -p $MODULE_PATH for mod in apache foreman foreman_proxy git passenger puppet tftp xinetd; do mkdir -p $MODULE_PATH/$mod wget http://github.com/theforeman/puppet-$mod/tarball/master -O - | tar xzvf - -C $MODULE_PATH/$mod --strip-components=1 done; echo include puppet, puppet::server, foreman, foreman_proxy | puppet apply --modulepath $MODULE_PATH Fails because the paths setup to download don't exist: ie http://yum.theforeman.org/stable/foreman-1.0.0-1.el6.noarch.rpm doesn't exist.
Updated by Ohad Levy almost 12 years ago
- Priority changed from Urgent to Normal
yes, this is what https://github.com/theforeman/puppet-foreman/pull/7 is fixing this issue.
so far the installer has not been fully updated as the deb packages are not avail yet.
stay tuned and it would be updated shortly, or if you prefer to apply the patch above to get it working with 1.0.
Updated by Chris Lee almost 12 years ago
Thanks so much, I'll try apply the patch manually and see how it goes.
Updated by Chris Lee almost 12 years ago
Just and FYI
applying the patch worked on a clean install of SL6 with out any problems
Updated by Sam Kottler almost 12 years ago
- Status changed from New to Pending
Great, thanks for testing it out!
Updated by Chris Lee almost 12 years ago
Hmm seems I spoke too soon
fI Finally got a chance to check everything again and while the patch worked and the install then works perfectly. Passenger doesn't work once it is done and the puppet clients all give errors such as when running puppet agent --test
err: Could not request certificate: Error 500 on SERVER: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
...
Updated by Ohad Levy almost 12 years ago
my guess this is because of the wrong config.ru, if no one else would beat me to it, I'll try to fix it later today.
Updated by Sam Kottler over 11 years ago
- Status changed from Pending to Closed
Closing this ticket out since it seems to be resolved. @Christian Holzheimer, if you're still having issues feel free to open it back up and we'll be sure to help.