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 1241760 - mod_ldap not installed during post-upgrade phase
Summary: mod_ldap not installed during post-upgrade phase
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-contents
Version: 6.7
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-07-10 04:09 UTC by Alois Mahdal
Modified: 2015-11-19 23:32 UTC (History)
6 users (show)

Fixed In Version: preupgrade-assistant-contents-0.6.41-1
Doc Type: Bug Fix
Doc Text:
Previously, mod_ldap module was not properly installed during the post-upgrade phase, even though it had been evaluated as "in use". This has now been fixed, and mod_ldap is properly installed.
Clone Of:
Environment:
Last Closed: 2015-11-19 23:32:17 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2498 0 normal SHIPPED_LIVE preupgrade-assistant-contents bug fix and enhancement update 2015-11-20 03:39:23 UTC

Description Alois Mahdal 2015-07-10 04:09:08 UTC 
Description of problem
======================

*mod_ldap* (and possibly) other modules may not have chance to get
installed during postupgrade phase, even though it has been evaluated as
"in use".

I have added a mockup LDAP config to /etc/httpd/conf.d, which triggered
the relevant solution text to explain that the module has split off to
new package and will be installed during post phase.

But in the post-upgrade phase *mod_ldap* has not been installed and there
is no mention about it--the postupgrade script has run, but installed
nothing--there is basically no log from it.


Version-Release number of selected component
============================================

preupgrade-assistant-contents-0.6.32-1.el6


Additional info
===============

My susipicion is that the post-upgade script might have incorrect (mixed
up somehow?) assumptions about the config dir structure:

  * during preupgrade scan, it looks for `LoadModule mod_ldap` in main
    conf and if found, looks for LDAP-related directives in both main
    and conf.d/* files

  * but during postupgrade.d, it looks for `LoadModule mod_ldap` again
    in the main file ... if the conf is RHEL7 that cannot succeed.
    The second part of the check is again `&&`-ed, and only looks in
    the main file, which also cannot succeed at all.
Comment 11 Alois Mahdal 2015-11-06 05:25:00 UTC 
Status update:

Patch has been created, tested, failed, fixed, tested, passed and is currently on its way to a proper build.

So we already know the patch works.

After build is ready, we will re-run tests to verify it has been integrated properly; if that's the case I expect tests to pass.
Comment 17 errata-xmlrpc 2015-11-19 23:32: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://rhn.redhat.com/errata/RHBA-2015-2498.html
Note You need to log in before you can comment on or make changes to this bug.