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 1744879 - 389ds automount issue
Summary: 389ds automount issue
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.9
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Pavel Březina
QA Contact: sssd-qe
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-08-23 05:25 UTC by snowfrs
Modified: 2019-09-02 13:14 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-08-27 19:09:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
389ds server and client configuration and the output log on client (8.34 KB, text/plain)
2019-08-23 05:25 UTC, snowfrs
no flags Details

Description snowfrs 2019-08-23 05:25:22 UTC
Created attachment 1607198 [details]
389ds server and client configuration and the output log on client

Description of problem:
SSSD on client truncating LDAP URI

Version-Release number of selected component (if applicable):
389ds server:
OS: CentOS Linux release 7.6.1810 (Core)
389ds: 389-ds-base-1.3.8.4-15.el7.x86_64
Client environment:
OS:  CentOS release 6.9 (Final)
openldap: openldap-clients-2.4.40-16.el6.x86_64
sssd:
sssd-client-1.13.3-60.el6.x86_64
sssd-ipa-1.13.3-60.el6.x86_64
sssd-proxy-1.13.3-60.el6.x86_64
sssd-common-1.13.3-60.el6.x86_64
sssd-common-pac-1.13.3-60.el6.x86_64
sssd-ad-1.13.3-60.el6.x86_64
sssd-ldap-1.13.3-60.el6.x86_64
python-sssdconfig-1.13.3-60.el6.noarch
sssd-krb5-common-1.13.3-60.el6.x86_64
sssd-krb5-1.13.3-60.el6.x86_64
sssd-1.13.3-60.el6.x86_64

How reproducible:
restart autofs on client to collect log

Steps to Reproduce:
1. configure 389ds server LDAP entry
2. configure sssd on client
3. restart sssd on client

Actual results:
sssd will ignore 389 if the ldap entry start with 389xxx

Expected results:


Additional info:

Comment 2 Chris Williams 2019-08-27 19:09:20 UTC
When Red Hat shipped 6.8 on May 10, 2016 RHEL 6 entered Maintenance Support 1 Phase.

https://access.redhat.com/support/policy/updates/errata/#Maintenance_Support_1_Phase 

That means only "Critical and Important Security errata advisories (RHSAs) and Urgent Priority Bug Fix errata advisories (RHBAs) may be released". 
Additionally Bugzilla is not a support tool and has no SLA. Please open a support case in the Red Hat Customer Portal where your issue can be investigated by Red Hat Support personnel.

Comment 3 Pavel Březina 2019-09-02 13:14:40 UTC
I tried to reproduce it with sssd-1.13, 1.16 and current master from SSSD side. In all versions, SSSD returns the correct information to automounter. Per previous comment, please use official support channel to investigate this further.


Note You need to log in before you can comment on or make changes to this bug.