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.

Bug 1417085

Summary: Support arbitrary configuration options for internal puppet classes in the installer
Product: Red Hat Satellite Reporter: Bryan Kearney <bkearney>
Component: InstallationAssignee: Stephen Benjamin <stbenjam>
Status: CLOSED ERRATA QA Contact: Shimon Shtein <sshtein>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.5CC: abelopez, bkearney, brubisch, chrobert, dgupte, egolov, hartsjc, howey.vernon, itewksbu, jcallaha, jnikolak, jpazdziora, katello-qa-list, kseifried, mlinden, mmccune, prsharma, pwayper, security-response-team, sreber, sshtein, stbenjam
Target Milestone: UnspecifiedKeywords: Security, Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1305782 Environment:
Last Closed: 2018-02-21 16:54:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1305782    
Bug Blocks: 1115190, 1211642, 1431631    

Comment 1 Satellite Program 2017-01-27 09:02:21 UTC 
Upstream bug assigned to stbenjam
Comment 2 Satellite Program 2017-01-27 09:02:33 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/16207 has been resolved.
Comment 3 James Hartsock 2017-03-06 14:11:57 UTC 
This also support the 'FileETag INode MTime Size' change to 'FileETag MTime Size' that is discussed in https://access.redhat.com/solutions/224713 ?
Comment 4 Stephen Benjamin 2017-03-06 14:24:21 UTC 
Hi James -

Unfortunately file_e_tag was only added to the Apache module in December:

  https://github.com/puppetlabs/puppetlabs-apache/blame/master/manifests/init.pp#L79

And it's not in any released version of the puppet module yet. So, it hasn't made it's way into the installer.

If you'd like, you can file a BZ and ask us to backport the file_e_tag feature into the version of puppetlabs-apache we're shipping with the installer.

Once it's eventually available, you can indeed do this in custom-hiera.yaml:

---
apache::file_e_tag: "MTime Size"
Comment 5 James Hartsock 2017-03-13 13:32:23 UTC 
In reply to Stephen Benjamin from comment #4)
> Hi James -
> 
> Unfortunately file_e_tag was only added to the Apache module in December:
> <snip>
> If you'd like, you can file a BZ and ask us to backport the file_e_tag
> feature into the version of puppetlabs-apache we're shipping with the
> installer.

Opened:
Bug 1431631 - Add FileETag to puppet Apache module
Comment 7 Satellite Program 2018-02-21 16:54:17 UTC 
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> 
> For information on the advisory, and where to find the updated files, follow the link below.
> 
> If the solution does not work for you, open a new bug report.
> 
> https://access.redhat.com/errata/RHSA-2018:0336