RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 1474514 - Yum updates of httpd package break links to run modules and logs
Summary: Yum updates of httpd package break links to run modules and logs
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: httpd
Version: 6.10
Hardware: All
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 20:04 UTC by Michael Kushnir
Modified: 2023-09-14 04:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-06 10:36:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Michael Kushnir 2017-07-24 20:04:20 UTC 
Description of problem:

When yum updates the httpd package, links (in /etc/httpd) for run, modules, and logs are reset to:

../../var/run/httpd
../../usr/lib64/httpd/modules
../../var/run/httpd

It generally seems foolish to use relative paths to point to critical system path locations such as logs and modules. For example, we have moved /etc/httpd to shared storage, so the ../ reference is constantly broken. 

We replace these links manually to point to the proper respective absolute path for these components:

/var/run/httpd
/usr/lib64/httpd/modules
/var/run/httpd

But, each update to the httpd package overwrites our links with the default, and again, foolish relative ../../ variants. 


How reproducible:

Very reproducable


Steps to Reproduce:
1. Install httpd
2. Change links for run, logs, and modules
3. Update httpd
4. See links reset to original relative paths 


Expected results:

Yum updates should not be overwriting user changed configuration links silently.
Comment 2 Joe Orton 2017-10-09 11:55:42 UTC 
You're right that these symlinks are immutable and hence shouldn't be in /etc.  I don't recall why they needed to be relative rather than absolute.

Probably the best way we could resolve this would be to move the default ServerRoot to /usr/lib/httpd and have 

/usr/lib/httpd/conf -> /etc/httpd/conf (and conf.d, conf.modules.d)
/usr/lib/httpd/logs -> /var/log/httpd
/usr/lib/httpd/modules -> /usr/lib64/httpd/modules
/usr/lib/httpd/logs -> /var/log/httpd

symlinks in place.

It would be useful to understand your use case better - when you say "we have moved /etc/httpd to shared storage" you mean you replaced /etc/httpd itself with a symlink, or something else?

That said, we don't plan to change the way this works at this point in the RHEL6 production lifecycle.
Comment 3 Jan Kurik 2017-12-06 10:36:51 UTC 
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/
Comment 4 Red Hat Bugzilla 2023-09-14 04:01:33 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.