Bug 1182331

Summary: [RFE] Updates overwrite important Web server configuration files
Product: Red Hat CloudForms Management Engine Reporter: Jared Deubel <jdeubel>
Component: ApplianceAssignee: Joe Rafaniello <jrafanie>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: low Docs Contact:
Priority: high    
Version: 5.4.0CC: abellott, bkozdemb, cpelland, jdeubel, jhardy, jrafanie, kbrock, ncarboni, obarenbo, xlecauch
Target Milestone: GAKeywords: FutureFeature
Target Release: 5.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Feature: Updates overwrite important Web server configuration files Reason: Meet requirement from STIG Result:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-03 17:47:35 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: 1244937    
Bug Blocks:    

Comment 5 Keenan Brock 2015-04-22 05:50:55 UTC
Would this be fixed by just setting these configuration files to be "configuration files"? (this is my silver bullet)

Comment 6 Joe Rafaniello 2015-04-22 14:09:34 UTC
If we don't need to change core apache settings like we recently changed keepalive, yes.  If we make changes, users/customers would have to migrate to the new config files on each appliance and possibly cause things to be DOA on upgrade.  I'd rather better understand what customers and users would be modifying in the configs and provide a way to externalize these changes in a separate config file that is loaded last.

Comment 8 Joe Rafaniello 2015-11-03 17:47:35 UTC
Closing.  We need to ship our configuration with the rpm as regular files so we can upgrade a complex of appliances without having to visit 10s of appliance to manually diff/apply configuration changes with each version upgrade.

Users could try the solution of storing their changes to the apache configuration in a uniquely named conf file that loads last such as /etc/httpd/conf.d/z_user.conf.  In this way, only this single file would need to be tested with each version upgrade to ensure newer cfme and apache versions still use the same syntax for the changes that the user wanted.