Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMaxim 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
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 ***
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