Bug 1302822

Summary:	Hiera 3.0.1 doesn't work immediately on install
Product:	[Fedora] Fedora EPEL	Reporter:	Ian Koenig <iguy>
Component:	hiera	Assignee:	Steve Traylen <steve.traylen>
Status:	CLOSED NEXTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	epel7	CC:	gchamoul, mastahnke, s, steve.traylen
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-06-01 14:04:32 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:

Description Ian Koenig 2016-01-28 17:27:15 UTC

Description of problem:

Installed Hiera 3.0.1 default from EPEL and ran hiera basic command to test it and it errors out with 

Failed to start Hiera: RuntimeError: Config file /etc/puppetlabs/code/hiera.yaml not found

The file supplied by the RPM is /etc/hiera.yaml which is not searched for in the code for hiera. 


Version-Release number of selected component (if applicable):
hiera-3.0.1-1.el7.noarch


How reproducible:
Everytime


Steps to Reproduce:
1.  yum install hiera
2.  hiera admin


Actual results:
Failed to start Hiera: RuntimeError: Config file /etc/puppetlabs/code/hiera.yaml not found

Expected results:
nil

Additional info:

Basically the default included file /etc/hiera.yaml should be in (or soft linked) to /etc/puppetlabs/code/hiera.yaml which is the new default location for hiera.

Comment 1 Steve Traylen 2017-06-01 14:04:32 UTC

Config file now moved and used in /etc/puppet/hiera.yaml to match fedora puppet package.