Hide Forgot
Description of problem: If the system is banned, "rhn-check -l" throws traceback. I guess this could be handled more gracefully ... Version-Release number of selected component (if applicable): rhn-setup-1.0.0-39.el6.noarch How reproducible: (haven't tried, the ban ended) Steps to Reproduce: 1. do something (?) nasty to get the system banned 2. rhn-channel -l Actual results: .qa.[root@ppcp-6s-0z-v1 tps]# rhn-channel -l Traceback (most recent call last): File "/usr/sbin/rhn-channel", line 98, in <module> main() File "/usr/sbin/rhn-channel", line 86, in main channels = map(lambda x: x['label'], getChannels().channels()) File "/usr/share/rhn/up2date_client/rhnChannel.py", line 99, in getChannels up2dateChannels = s.up2date.listChannels(up2dateAuth.getSystemId()) File "/usr/share/rhn/up2date_client/rhnserver.py", line 52, in __call__ raise self.__exception_from_fault(f) up2date_client.up2dateErrors.AbuseError: Error Message: Abuse of Service detected for server ppcp-6s-0z-v1.ss.eng.bos.redhat.com (1016580813) Error Class Code: 49 Error Class Info: You are getting this error because RHN has detected an abuse of service from this system and account. This error is triggered when your system makes too many connections to Red Hat Network. This error can not be triggered under a normal use of the Red Hat Network service as configured by default on Red Hat Linux. The Red Hat Network services for this system will remain disabled until you will reduce the RHN network traffic from your system to acceptable limits. Please log into RHN and visit https://rhn.redhat.com/help/contact.pxt to contact technical support if you think you have received this message in error. Expected results: (the same error messages without the traceback at the beginning) Additional info:
Setting devel ack, to try to fix the issue.
spacewalk.git d8936ff299f62b5821cb35d3e18b81291d75fbc7 cherrypicked to satellite.git as 429afd631728b60f4d620ed07164ab614b941881
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/RHBA-2012-0752.html