- Email: email@example.com
- Registered on: 05/12/2011
- Last connection: 11/08/2013
- 03:47 PM Foreman Bug #4028 (Closed): foreman-rake puppet:rdoc:generate aborts
- Dupe of #1556
- 03:43 PM Foreman Bug #4028 (Closed): foreman-rake puppet:rdoc:generate aborts
- CentOS 6, Puppet 2.7.23, Foreman 1.3.2...
- 09:15 PM Foreman Feature #3203 (Closed): Request for vCloud Director support
- After thorough review of the documentation and experimentation, I don't think this integration is feasible. Perhaps ...
- 05:55 PM Installer Revision 222fb5e5 (puppet-foreman): Make use of $foreman::params::server_ssl_* in vhost conf.
- 10:11 PM Foreman Feature #3203: Request for vCloud Director support
- I have fog 1.18 up and running on a CentOS 6 box using the ruby193 software collection. I've been experimenting with...
- 10:36 PM Foreman Bug #3576: db:migrate fails when upgrading directly from 0.4.2 to 1.3.0
- Test environment:
CentOS 6, MySQL 5.1, Puppet 2.7
If it would be useful, I have a 570KB dump of my combined puppe...
- 10:23 PM Foreman Bug #3576 (Resolved): db:migrate fails when upgrading directly from 0.4.2 to 1.3.0
- I'm using the puppet-foreman module to upgrade an ancient foreman installation, but Exec["dbmigrate"] fails with:
- 01:43 PM Foreman Feature #985 (Resolved): no permission corresponds to 'Run Puppet' feature
- <amh-mw> What permissions does a role need to be able to use the 'Run Puppet' feature? I can use the feature as admi...
Also available in: Atom