Bug 1302822 - Hiera 3.0.1 doesn't work immediately on install
Summary: Hiera 3.0.1 doesn't work immediately on install
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: hiera
Version: epel7
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Steve Traylen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-28 17:27 UTC by Ian Koenig
Modified: 2017-06-01 14:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-01 14:04:32 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.