Bug 1121697

Summary:	Missing configuration symlink for settings.d
Product:	Red Hat OpenStack	Reporter:	John Eckersberg <jeckersb>
Component:	foreman-proxy	Assignee:	Mike Burns <mburns>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Omri Hochman <ohochman>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Foreman (RHEL 6)	CC:	hlawatschek, jeckersb, mburns, rhos-maint
Target Milestone:	---	Keywords:	ZStream
Target Release:	Installer
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-04-30 16:47:35 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1121172

Description John Eckersberg 2014-07-21 15:43:17 UTC

The foreman-proxy rpm contains a symlink for the settings.yml file:

# ls -l /usr/share/foreman-proxy/config/settings.yml 
lrwxrwxrwx. 1 root root 31 Jul 18 15:58 /usr/share/foreman-proxy/config/settings.yml -> /etc/foreman-proxy/settings.yml

However there is no symlink to the settings.d directory, thus the proxy cannot find the plugin config files:

]# ls -l /etc/foreman-proxy/settings.d/
total 36
-rw-r--r--. 1 root root  263 Jul 21 10:08 bmc.yml
-rw-r--r--. 1 root root  320 Jul 21 11:31 chef.yml
-rw-r--r--. 1 root root  713 Jul 21 10:08 dhcp.yml
-rw-r--r--. 1 root root  660 Jul 21 10:08 dns.yml
-rw-r--r--. 1 root root  130 Jul 21 10:08 puppetca.yml
-rw-r--r--. 1 root root 1041 Jul 21 10:08 puppet.yml
-rw-r--r--. 1 root root  321 Jul 21 10:08 realm.yml
-rw-r--r--. 1 root root  167 Jul 21 10:08 tftp.yml

And turning on debug logging for the proxy generates the following in the proxy log:

W, [2014-07-21T11:29:37.515366 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/foreman_proxy.yml. Using default settings.
I, [2014-07-21T11:29:37.515526 #14772]  INFO -- : 'foreman_proxy' settings were initialized with default values: :enabled: true
W, [2014-07-21T11:29:37.518497 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/dns.yml. Using default settings.
I, [2014-07-21T11:29:37.518629 #14772]  INFO -- : 'dns' module is disabled.
W, [2014-07-21T11:29:37.518725 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/tftp.yml. Using default settings.
I, [2014-07-21T11:29:37.518822 #14772]  INFO -- : 'tftp' module is disabled.
W, [2014-07-21T11:29:37.518913 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/dhcp.yml. Using default settings.
I, [2014-07-21T11:29:37.519035 #14772]  INFO -- : 'dhcp' module is disabled.
W, [2014-07-21T11:29:37.519128 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/puppetca.yml. Using default settings.
I, [2014-07-21T11:29:37.519247 #14772]  INFO -- : 'puppetca' module is disabled.
W, [2014-07-21T11:29:37.519339 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/puppet.yml. Using default settings.
I, [2014-07-21T11:29:37.519459 #14772]  INFO -- : 'puppet' module is disabled.
W, [2014-07-21T11:29:37.519552 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/bmc.yml. Using default settings.
I, [2014-07-21T11:29:37.519646 #14772]  INFO -- : 'bmc' module is disabled.
W, [2014-07-21T11:29:37.519736 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/chef.yml. Using default settings.
I, [2014-07-21T11:29:37.519817 #14772]  INFO -- : 'chefproxy' module is disabled.
W, [2014-07-21T11:29:37.519908 #14772]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/realm.yml. Using default settings.
I, [2014-07-21T11:29:37.520029 #14772]  INFO -- : 'realm' module is disabled.


Adding the symlink manually corrects this, and the plugins load as expected:

W, [2014-07-21T11:30:34.589161 #14856]  WARN -- : Couldn't find settings file /usr/share/foreman-proxy/config/settings.d/foreman_proxy.yml. Using default settings.
I, [2014-07-21T11:30:34.589352 #14856]  INFO -- : 'foreman_proxy' settings were initialized with default values: :enabled: true
I, [2014-07-21T11:30:34.592817 #14856]  INFO -- : 'dns' settings were initialized with default values: :dns_provider: nsupdate
I, [2014-07-21T11:30:34.595974 #14856]  INFO -- : 'tftp' settings were initialized with default values: :tftproot: /var/lib/tftpboot
I, [2014-07-21T11:30:34.599152 #14856]  INFO -- : 'dhcp' settings were initialized with default values: :dhcp_provider: isc
I, [2014-07-21T11:30:34.602306 #14856]  INFO -- : 'puppetca' settings were initialized with default values: :puppetdir: /etc/puppet, :ssldir: /var/lib/puppet/ssl
I, [2014-07-21T11:30:34.605611 #14856]  INFO -- : 'puppet' settings were initialized with default values: :puppet_provider: puppetrun, :puppetdir: /etc/puppet
I, [2014-07-21T11:30:34.635900 #14856]  INFO -- : 'realm' settings were initialized with default values: :realm_provider: freeipa


Version-Release number of selected component (if applicable):
foreman-proxy-1.6.0.21-1.el6sat.noarch

Comment 3 Mike Burns 2015-04-30 16:22:13 UTC

Eck,  what's the consequence of this?

Comment 4 John Eckersberg 2015-04-30 16:37:06 UTC

(In reply to Mike Burns from comment #3)
> Eck,  what's the consequence of this?

It's been a while so a bit of a stretch remembering...

I believe at the time it basically broke all the things, because foreman-proxy didn't work right so everything which relied on foreman-proxy was also broken.

However, we've been using foreman-proxy successfully now for the better part of a year since I've filed this, so something along the way must have made this bug go away.

So, +1 from me if you want to just close this out.  I don't think it's a problem anymore.

Comment 5 Mike Burns 2015-04-30 16:47:35 UTC

great, thanks!