Bug 1603241 - Provisioning template tries to write puppet.conf to wrong directory
Summary: Provisioning template tries to write puppet.conf to wrong directory
Keywords:
Status: CLOSED DUPLICATE of bug 1599343
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Provisioning Templates
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-19 14:03 UTC by Maxim Burgerhout
Modified: 2018-07-20 06:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-07-20 06:37:24 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
puppet.log (5.00 KB, text/plain)
2018-07-19 14:03 UTC, Maxim Burgerhout
no flags Details
kickstart screenshot (11.12 KB, image/png)
2018-07-19 14:03 UTC, Maxim Burgerhout
no flags Details

Description Maxim Burgerhout 2018-07-19 14:03:22 UTC
Created attachment 1460053 [details]
puppet.log

Description of problem:
It looks like the kickstart default provisioning template (and puppet_setup and puppet.conf) try to write the puppet.conf file to /etc/puppet, instead of to /etc/puppetlabs/puppet.


Version-Release number of selected component (if applicable):
6.4.0 SNAP 12

How reproducible:


Steps to Reproduce:
1. install new machine
2. check output of kickstart and puppet logs afterwards
3.

Actual results:
error in kickstart (see screenshot attachment)
errors in logs (see text attachment)

Expected results:
All good from the start

Additional info:
situation seems to correct itself, haven't looked into how this happens: on second puppet run all is fine

Comment 1 Maxim Burgerhout 2018-07-19 14:03:42 UTC
Created attachment 1460054 [details]
kickstart screenshot

Comment 3 Marek Hulan 2018-07-20 06:37:24 UTC
Thanks for the report Maxim, this is a valid bug. This was caused by the fact the new templates defaults to use puppet 3. This is being resolved by BZ 1599343 where we seed the global parameter that tells puppet 5 is enabled by default. Closing as dup of it.

*** This bug has been marked as a duplicate of bug 1599343 ***


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