Red Hat Bugzilla – Bug 895615
ipa-client-automount: autofs failed in s390x and ppc64 platform
Last modified: 2013-02-21 04:43:39 EST
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:
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
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
Upstream ticket: https://fedorahosted.org/sssd/ticket/1770
test automated. beaker run: https://beaker.engineering.redhat.com/jobs/371069 https://beaker.engineering.redhat.com/jobs/371070
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