Activity
From 08/16/2015 to 09/14/2015
09/11/2015
- 08:05 AM Feature #11781 (Closed): Add smart-proxy 1.10 configuration options
- * dhcp_server from #11676
09/09/2015
- 05:53 AM Bug #11726 (Rejected): Installer --foreman-proxy-puppet-ssl-* flags applied to wrong settings file
- Thanks!
- 05:44 AM Bug #11726: Installer --foreman-proxy-puppet-ssl-* flags applied to wrong settings file
- Thanks! You were right. Corrected this and it works now. The bug can be closed as invalid!
09/08/2015
- 12:23 PM Feature #11735 (New): As a user, I want foreman-installer to provide a scenario for installing a smart-proxy
- This is an enhancement to leverage the Kafo changes provided by http://projects.theforeman.org/issues/10162 to suppor...
- 08:45 AM Bug #11726 (Need more information): Installer --foreman-proxy-puppet-ssl-* flags applied to wrong settings file
- I think you may be confusing two different sets of configuration options.
--foreman-proxy-ssl-* are used in settin... - 08:39 AM Bug #11726 (Rejected): Installer --foreman-proxy-puppet-ssl-* flags applied to wrong settings file
- Foreman-installer only applies --foreman-proxy-ssl-ca, --foreman-proxy-ssl-cert and/or --foreman-proxy-ssl-key to /et...
09/04/2015
- 03:02 AM Bug #11681 (Closed): foreman, candlepin, gutterball databases use default encoding vs explicit UTF8
09/03/2015
- 03:11 PM Bug #11681 (Closed): foreman, candlepin, gutterball databases use default encoding vs explicit UTF8
- Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1255520
Description of problem:
It appears when we crea...
09/02/2015
- 06:52 AM Bug #11655 (Closed): DNS configuration for smart proxy split into per-provider configs
- #7008 split the smart proxy DNS configuration into per-provider configuration files and also changed settings such as...
- 05:08 AM Bug #11652 (Closed): Foreman installer sets Apache2 SSLCACertificatePath to system Trust Store
- The SSLCACertificatePath of the foreman ssl and puppet master vhost is set to the System Trust Store.
On debian this...
08/19/2015
- 01:49 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- On https://<fqdn>/smart_proxies I have attempted to create proxy per
http://projects.theforeman.org/projects/smart...
08/18/2015
- 09:21 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- Does the smart proxy register if you do it now, manually? (since it now says foreman-proxy (pid 10918) is running...)
- 09:13 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- OK, did 10 installs and 9th failed (10th still running).
On the failed system:... - 03:41 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- /var/log/foreman-proxy/access.log is empty and proxy.log only have this:
# Logfile created on Mon Aug 17 16:49:18 ... - 03:09 AM Bug #11331 (Need more information): foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- Can you attach the foreman-proxy log? Is the service running after the installer has run? If not, test it and check...
- 02:40 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- And katello-installer.log from same run as in comment #15 above
- 02:33 AM Bug #11331: foreman_smartproxy: failed to call refresh: missing param 'id' in parameters after ensure failure
- Encountered it again. Attaching production.log.
Also available in: Atom