Hide Forgot
Description of problem: authconfig fails to enable sssd on ppc64 Version-Release number of selected component (if applicable): authconfig-5.3.21-7.el5 sssd-1.5.1-37.el5 Beaker Distro: RHEL5.7-Server-20110616.0.n How reproducible: Always Steps to Reproduce: 1. # arch ppc64 2. # rpm -qf /lib64/security/pam_sss.so sssd-client-1.5.1-37.el5 3. #authconfig --enablesssd --enablesssdauth --updateall authconfig: Authentication module /lib/security/pam_sss.so is missing. Authentication process will not work correctly. Stopping sssd: cat: /var/run/sssd.pid: No such file or directory [FAILED] Starting sssd: [ OK ] [ OK ] Actual results: authconfig fails to enable sssd on ppc64 Expected results: authconfig should enable sssd on ppc64 Additional info:
This looks like an authconfig issue. It's trying to locate pam_sss.so in the wrong directory. lib->lib64
No, on RHEL-5 the primary architecture on PPC is the 32bit. For the sssd support you have to have 32 bit sssd-client package installed.
reopening and assigning back to sssd component
(In reply to comment #2) > No, on RHEL-5 the primary architecture on PPC is the 32bit. For the sssd > support you have to have 32 bit sssd-client package installed. I don't understand this statement. On a PPC64 installation, the primary arch is .ppc instead of .ppc64? That doesn't make any sense. And even if that was the case, SSSD has Requires: sssd-client. Wouldn't RPM default to using the primary arch if two are available?
It makes sense - the ppc64 userspace does not bring any performance improvements - quite the opposite - to the ppc userspace. And that was the main reason for making the ppc arch primary on PPC64 platform. Note though that RHEL-6 is different in this regard - there the ppc64 is primary possibly to make it more similar to x86_64. As for the RPM behavior, I do not know, it might well be a glitch/bug in RPM in RHEL-5.
Kaushik, I can only reproduce this if I have: sssd-1.5.1-37.el5.ppc sssd-client-1.5.1-37.el5.ppc64 However, if you just 'yum install sssd', you get: sssd-1.5.1-37.el5.ppc sssd-client-1.5.1-37.el5.ppc In this setup, everything works correctly. (It also works correctly if both arches of sssd-client are installed). Could you please check whether your install script is doing something incorrect here? (Like 'yum install sssd sssd-client.ppc64')
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update. Contact your manager or support representative in case you need to escalate this bug.
(In reply to comment #6) > Could you please check whether your install script is doing something incorrect > here? (Like 'yum install sssd sssd-client.ppc64') Even before my automation scripts install sssd, it seems beaker already installs sssd.ppc & sssd-client.ppc64 when you run the automation scripts. This looks like a beaker issue during automation run, since reserving a beaker machine for ppc64 doesn't install sssd though. On reserving a beaker machine, and doing "yum install sssd" works fine for me too. I have now modified my automation scripts to explicitly install sssd-client.ppc(for rhel5.7 ppc64 only) and they seem to be running fine.
Based on comment #8, closing this as NOTABUG.