Bug 219357
Summary: | RHNSat5 - rhn_register fails if using PAM authentication | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Matt Domsch <matt_domsch> |
Component: | Server | Assignee: | James Slagle <jslagle> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Corey Welton <cwelton> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 500 | CC: | dduffey, jpazdziora, ltroan, paul.boin, rhn-bugs, sbenjamin, wwlinuxengineering |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | sat500 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-06-26 02:25:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 232328 |
Description
Matt Domsch
2006-12-12 19:27:19 UTC
/var/log/debug indicates that the PAM authentication step is succeeding, but for some reason the xmlrpc call is reporting a failure after that. I'm looking... This failure is impacting Dell's ability to test RHEL5 betas. Please respond ASAP. Everything else about the Satellite Server is working, except the ability to register systems to it when using PAM authentication. The RHEL5 client failure can't print out a good error report either, it tracebacks. [Tue Dec 12 16:28:50 2006] rhn_register Traceback (most recent call last): File "/usr/share/rhn/up2date_client/tui.py", line 1213, in __init__ rhnreg.registerUser(tui.userName, tui.password, tui.email) File "/usr/share/rhn/up2date_client/rhnreg.py", line 222, in registerUser s.registration.new_user(username, password, email) File "/usr/share/rhn/up2date_client/rhnserver.py", line 62, in __call__ message = pieces[2].strip(" '") exceptions.IndexError: list index out of range Stubbing out /usr/share/rhn/server/rhnUser.pm:new_user() to always return 0 causes the RHEL5 client to make it one step further such that it then fails at registerServer2. Stubbing out same doesn't change RHEL3 or 4 client behavior. [Tue Dec 12 17:24:32 2006] rhn_register Traceback (most recent call last): File "/usr/share/rhn/up2date_client/tui.py", line 1229, in __init__ other = self.tui.other) File "/usr/share/rhn/up2date_client/rhnreg.py", line 367, in registerSystem2 other) File "/usr/share/rhn/up2date_client/rhnserver.py", line 62, in __call__ message = pieces[2].strip(" '") exceptions.IndexError: list index out of range I reproduced the issue and figured out a work-around. For some reason the PyPAM module needs to have pam-devel installed in order to work. We're still trying to figure out why exactly that is, but as a work-around you can do an 'up2date pam-devel' on the satellite followed by a satellite restart and rhn_register should work for PAM authenticated users. John, yes, thanks, this workaround does work for me too. Thanks for your quick response! Leaving open until the root cause is found. I saw something similar here. Sat. Server 4.1.5 wouldn't let me rhnpush my packages into a custom channel. I disabled PAM, and it worked. I added pam-devel and re-enabled PAM, and it also worked. So, maybe pam-devel should be a pre-requisite? *** Bug 216865 has been marked as a duplicate of this bug. *** Updated version of PyPAM released with satellite which includes a fix for PAM authentication working without requiring pam-devel. This will be releasd with RHN Satellite 5.0 QA Verified - can now register w/ PAM-auth'ed users. release_pending Closed for Satellite 500 Release. |