Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
(In reply to comment #3)
> hi Ian,
> Could you illustrate the detailed problem and if QE still use bz563956 to do
> verification?
Sorry, I've removed the RHTSDone entry for now.
Once I work out what is going wrong and fix it I'll need to
write a specific test that checks function on the two archs
concerned.
(In reply to comment #4)
> (In reply to comment #3)
> > hi Ian,
> > Could you illustrate the detailed problem and if QE still use bz563956 to do
> > verification?
>
> Sorry, I've removed the RHTSDone entry for now.
> Once I work out what is going wrong and fix it I'll need to
> write a specific test that checks function on the two archs
> concerned.
This last comment is incorrect.
We have another bug to cover the case I was referring to above.
The bugzillas test bz563956 has been updated to check autofs
function with LDAP configurations that caused a problem during
RHEL-5 development, the reason for raising this bug.
The problem was related to limits set on the LDAP server and the
interaction between soft and hard limit settings and the need for
autofs to adjust the number of results requested to suite these
settings. You can see these setting being set in test bz563956 to
check that autofs functions with them.
So, the autofs bugzillas test bz563956 can be used to verify this
bug.
Ian
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.
http://rhn.redhat.com/errata/RHBA-2011-1723.html