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 895615 - ipa-client-automount: autofs failed in s390x and ppc64 platform
Summary: ipa-client-automount: autofs failed in s390x and ppc64 platform
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sssd
Version: 6.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 902691
TreeView+ depends on / blocked
 
Reported: 2013-01-15 16:34 UTC by Yi Zhang
Modified: 2020-05-02 17:14 UTC (History)
8 users (show)

Fixed In Version: sssd-1.9.2-73.el6
Doc Type: Bug Fix
Doc Text:
No documentation needed.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:43:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2812 0 None closed ipa-client-automount: autofs failed in s390x and ppc64 platform 2020-05-02 17:14:47 UTC
Red Hat Product Errata RHSA-2013:0508 0 normal SHIPPED_LIVE Low: sssd security, bug fix and enhancement update 2013-02-20 21:30:10 UTC

Description Yi Zhang 2013-01-15 16:34:06 UTC
Description of problem: autofs mount failed on s390x and ppc64.
the following log message appears on /var/log/messages

Jan 15 10:51:19 ibm-z10-32 automount[23613]: lookup_read_master: lookup(sss): getautomntent_r: Invalid argument
Jan 15 10:51:19 ibm-z10-32 automount[23613]: setautomntent: lookup(sss): setautomntent: No such file or directory
Jan 15 10:51:19 ibm-z10-32 automount[23613]: lookup_read_master: lookup(sss): getautomntent_r: Invalid argument




Version-Release number of selected component (if applicable):
ipa-client-3.0.0-21.el6.x86_64
ipa-server-3.0.0-21.el6.x86_64
sssd-client-1.9.2-68.el6.x86_64
sssd-1.9.2-68.el6.x86_64

How reproducible: always


Steps to Reproduce: need find out, the above error msg found in autoamation. the exact statement that triggers it is unknow for now. 
  
Actual results:


Expected results:


Additional info:

Comment 2 Yi Zhang 2013-01-15 18:00:07 UTC
what i confirmed:
1. this is sssd bug
2. the above error message happens when do ipa-client-automount install

[root@ibm-z10-34 ~] tail -f /var/log/message | grep "automount"
[root@ibm-z10-34 ~]# ipa-client-automount --server=qe-blade-14.testrelm.com --location=Indirect_use_sssd_16836
IPA server: qe-blade-14.testrelm.com
Location: Indirect_use_sssd_16836
Continue to configure the system with these values? [no]: yes
Configured /etc/nsswitch.conf
Configured /etc/sysconfig/nfs
Configured /etc/idmapd.conf
Started rpcidmapd
Started rpcgssd
Restarting sssd, waiting for it to become available.
Jan 15 12:52:34 ibm-z10-34 automount[21908]: lookup_read_master: lookup(sss): getautomntent_r: Invalid argument
Jan 15 12:52:34 ibm-z10-34 automount[21908]: setautomntent: lookup(sss): setautomntent: No such file or directory
Jan 15 12:52:35 ibm-z10-34 automount[21908]: lookup_read_master: lookup(sss): getautomntent_r: Invalid argument
Started autofs
[root@ibm-z10-34 ~]# cd /ipashare_25905
-bash: cd: /ipashare_25905: No such file or directory

======== automount location has no problem ===
[root@qe-blade-14 ~]# ipa automountlocation-tofiles Indirect_use_sssd_16836
/etc/auto.master:
/-	/etc/auto.direct
/ipashare_25905	/etc/auto.share
---------------------------
/etc/auto.direct:
---------------------------
/etc/auto.share:
public_16952	-rw,soft,rsize=8192,wsize=8192  cloud-qe-1.testrelm.com:/share/pub

maps not connected to /etc/auto.master:

=== [ commands to create above map, for bug verification use ] ===
1. kinit admin
2. ipa automountlocation-add Indirect_use_sssd_16836
3. ipa automountmap-add Indirect_use_sssd_16836 auto.share
4. ipa automountkey-add Indirect_use_sssd_16836 auto.master --key=/ipashare_25905 --info=auto.share
5. ipa automountkey-add Indirect_use_sssd_16836 auto.share  --key=public_16952 --info="-rw,soft,rsize=8192,wsize=8192  cloud-qe-1.testrelm.com:/share/pub"
6. ipa automountlocation-tofiles Indirect_use_sssd_16836

don't forget the /etc/export on NFS server
/share *(rw,async,fsid=0,no_subtree_check,no_root_squash)

=== [ build information ] ===
[root@ibm-z10-34 ~]# rpm -qa | grep sssd
sssd-1.9.2-68.el6.s390x
sssd-client-1.9.2-68.el6.s390x
[root@ibm-z10-34 ~]# rpm -qa | grep autofs
libsss_autofs-1.9.2-68.el6.s390x
autofs-5.0.5-73.el6.s390x

Comment 3 Yi Zhang 2013-01-15 18:05:46 UTC
additional test:

same automount map, use "--no-sssd", the install success, no error msg being triggered, and autofs works good.

ipa-client-automount --server=qe-blade-14.testrelm.com --location=Indirect_use_sssd_16836 --no-sssd

Comment 4 Jakub Hrozek 2013-01-16 08:24:19 UTC
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1770

Comment 10 errata-xmlrpc 2013-02-21 09:43:39 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.

http://rhn.redhat.com/errata/RHSA-2013-0508.html


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