Description of problem:
In case of timeout from Hosted when activating Satellite, misleading error message "There was a problem validating the satellite certificate: 89" is printed.


Version-Release number of selected component (if applicable):
spacewalk-setup-2.0.1-7.el5sat


How reproducible:
usually when you get timeout from Hosted


Steps to Reproduce:
1. Install connected satellite and get timeout from hosted when activating it


Actual results:
[...]
* Activating Red Hat Satellite.
** Loading Red Hat Satellite Certificate.
** Verifying certificate locally.
** Activating Red Hat Satellite.

There was a problem validating the satellite certificate: 89


In rhn_installation.log there is:
[...]
RHN_PARENT: satellite.rhn.redhat.com

ERROR: Timeout Exception


Expected results:
Error should express that this was timeout.


Additional info:
In spacewalk/setup/bin/spacewalk-setup there is:
  my %retcodes = (
		  10 => 'Could not parse certificate file',
		  [...]
		  86 => "$product_name has no base channel on parent server",
		  87 => "No $product_name channel available for this version",
		  127 => 'Unhandled error',
		 );

  if ($ret) {
    my $exit_value = $? >> 8;

    die "(satellite_activation_failed) $retcodes{$exit_value}\n\n"
      if exists $retcodes{$exit_value};

    die "There was a problem validating the satellite certificate: $exit_value\n\n";
  }

In backend/satellite_tools/rhn-satellite-activate we basically just call rhn_satellite_activate.py.

In backend/satellite_tools/rhn_satellite_activate.py there is:
            except TimeoutException, e:
                writeError(e)
                return 89

I do not consider this important for 5.6.0 release.