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.
Set installer component but please move to the component that more aligns with the request.
The request here is to allow for the installer to not prune specific files that are configured. For example, if a customer configures other information in the port 80 vhost on a Capsule to allow it to serve other directories, that configuration will work for them until the installer is run, at which point the installer will filebucket that file back to it's original configuration. This request would be to allow for a customer to set a filename to not be filebucketed when the installer is run, so that those configurations are not overridden.
Can you please expand on what you are trying and want to host on your Satellite / Capsule? Our goal is to have the Satellite and Capsule treated as appliances, so insight into your use case helps us with prioritization and understanding.
Satellite and Capsule Apache configurations are critical to the operation of the application. We do not plan to support open customization of the Vhosts and any changes to the Apache configuration outside of the installer results in an unsupported configuration.
If you can provide specific examples of what changes to the Vhost or the type of additional files desired to be served via the Satellite and Capsule's Apache then please re-open with that information.