Bug 1302822 - Hiera 3.0.1 doesn't work immediately on install
Hiera 3.0.1 doesn't work immediately on install
Status: CLOSED NEXTRELEASE
Product: Fedora EPEL
Classification: Fedora
Component: hiera (Show other bugs)
epel7
All Linux
unspecified Severity high
: ---
: ---
Assigned To: Steve Traylen
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-01-28 12:27 EST by Ian Koenig
Modified: 2017-06-01 10:04 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-01 10:04:32 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ian Koenig 2016-01-28 12:27:15 EST
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 10:04:32 EDT
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.