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.
Bug 1371093 - capsule installer is removing puppet.conf environment
Summary: capsule installer is removing puppet.conf environment
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks: 1122832
TreeView+ depends on / blocked
 
Reported: 2016-08-29 10:09 UTC by Peter Vreman
Modified: 2018-09-04 17:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-09-04 17:44:40 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 16919 0 None None None 2016-10-13 16:17:28 UTC

Description Peter Vreman 2016-08-29 10:09:28 UTC 
Description of problem:
The capsule installer is remvoing the environment setting of puppet. This is a setting that contains the puppet environment as managed by Satellite itself. The capsule feature does not use it and it shall therefor keep the old value.

We manage the puppet.conf to set the environment to the expected KT_ environment so the correct environment is used also during the puppet plugin (facts .rb files) downloading. And also that the user can do a "puppet agent -t -v" runs is without taking care of setting the correct environment.

Below is the output when (re-)running satellite-installer --scenario=capsule

[ WARN 2016-08-29 10:01:15 verbose]  /Stage[main]/Puppet::Config/Concat[/etc/puppet/puppet.conf]/File[/etc/puppet/puppet.conf]/content:
[ INFO 2016-08-29 10:01:15 verbose] --- /etc/puppet/puppet.conf 2016-08-26 12:16:38.107374178 +0000
[ INFO 2016-08-29 10:01:15 verbose] +++ /tmp/puppet-file20160829-13497-sxpk6c-0 2016-08-29 10:01:15.728826271 +0000
[ INFO 2016-08-29 10:01:15 verbose] @@ -55,7 +55,7 @@
[ INFO 2016-08-29 10:01:15 verbose]      report            = true
[ INFO 2016-08-29 10:01:15 verbose]      pluginsync        = true
[ INFO 2016-08-29 10:01:15 verbose]      masterport        = 8140
[ INFO 2016-08-29 10:01:15 verbose] -    environment       = KT_Hilti_Library_hg_crash__Infra__Sat6Sandbox_Capsule_58
[ INFO 2016-08-29 10:01:15 verbose] +    environment       = production
[ INFO 2016-08-29 10:01:15 verbose]      certname          = li-lc-1589.hag.hilti.com
[ INFO 2016-08-29 10:01:15 verbose]      server            = li-lc-1589.hag.hilti.com
[ INFO 2016-08-29 10:01:15 verbose]      listen            = false
[ INFO 2016-08-29 10:01:15 verbose]  Computing checksum on file /etc/puppet/puppet.conf

Proposal for a fix is to create a fact with the current puppet environment and then use that fact in the puppet.conf.erb file.


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


How reproducible:


Steps to Reproduce:
1. Create server attach to Sat6 managed with puppet
2. Have a puppet module to also manage the puppet.conf to set the environment to the expected KT_ environment.
3. Run "satellite-installer --scenario=capsule" o the capsule

Actual results:
puppet.conf environment setting is reverted back to "production"

Expected results:
the existing puppet.conf environment setting is untouched


Additional info:
Comment 2 Stephen Benjamin 2016-10-13 16:16:54 UTC 
If we exposed the "puppet" puppet module at the top level of the installer, it would solve it, as this is configurable:

https://github.com/theforeman/puppet-puppet/blob/master/manifests/init.pp#L224
Comment 3 Stephen Benjamin 2016-10-13 16:17:26 UTC 
Created redmine issue http://projects.theforeman.org/issues/16919 from this bug
Comment 4 Peter Vreman 2016-10-14 08:05:00 UTC 
Having a puppet environment specifiable on the satellite-installer level does not help, because the KT_ environment name generated by the Katello content views is unpredictable for the end user.

At least if an environment is set it shall not change it or the default at the satellie-installer shall be the existing environment. In my custom puppet modules i use a fact to expose the current puppet enviornment. And then write this one back in the puppet.conf when it is not overriden with an other parameter.
Comment 5 Bryan Kearney 2018-09-04 17:44:40 UTC 
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the foreseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Note You need to log in before you can comment on or make changes to this bug.