+++ This bug was initially created as a clone of Bug #849150 +++

Description of problem:
Command "spacewalk-channel" seems to be too verbose when simply restricts the user from a certain action. In this case messages like "An error has occurred while processing your request." are inappropriate.

Version-Release number of selected component (if applicable):
rhn-setup-1.0.0-71.el6.noarch.rpm
rhn-setup-0.4.20-78.el5


How reproducible:
100%

Steps to Reproduce:
1. stalltie-sync -c rhel-x86_64-server-6 -c rhn-tools-rhel-x86_64-server-6 -c redhat-rhn-proxy-5.4-server-x86_64-6
2. Register client to Satellite
3. Execute the following command on the client.
  #spacewalk-channel --add -c redhat-rhn-proxy-5.4-server-x86_64-6 --user admin --password nimda
  
Actual results:

# spacewalk-channel --add -c redhat-rhn-proxy-5.4-server-x86_64-6 --user admin --password nimda
Error communicating with server. The message was:

Error Class Code: 73
Error Class Info: Satellite or Proxy channel can not be subscribed.
Explanation: 
     An error has occurred while processing your request. If this problem
     persists please enter a bug report at bugzilla.redhat.com.
     If you choose to submit the bug report, please be sure to include
     details of what you were trying to do when this error occurred and
     details on how to reproduce this problem.

Expected results:
# spacewalk-channel --add -c redhat-rhn-proxy-5.4-server-x86_64-6 --user admin --password nimda
Error communicating with server. The message was:

Error Class Code: 73
Error Class Info: Satellite or Proxy channel can not be subscribed.

Additional info:

--- Additional comment from sherr on 2012-08-17 13:56:23 EDT ---

This is an incredibly easy thing to fix if we want to pull this into Sat 5.5.

All we have to do is change a rhnFault(73) to rhnFault(73, explain=0).

So there is virtually 0 risk of breaking something else if we're worried about regressions.