Red Hat Bugzilla – Bug 58999
invalid server certificate
Last modified: 2015-01-07 18:54:47 EST
Description of problem:
A registered system executing `up2date clearcase-config` results in an error.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. execute `up2date clearcase-config`
Actual Results: A dialog box popped up asking for confirmation of installation
of the Red Hat, Inc. public key. I clicked yes, and next, the dialog box
closed and the terminal had an error on it.
[root@b2-lnx /root]# up2date clearcase-config
Retrieving list of all available packages...
There was a fatal error communicating with the server. The message was:
Error Class Code: 9
Error Class Info: Invalid Server Certificate.
An error has occurred while processing your request. If this problem
persists please submit a bug report to firstname.lastname@example.org.
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: The clearcase-config package should've been downloaded from
the proxy server and installed.
On the registered client machine, /etc/sysconfig/rhn/up2date points to the
[root@b2-lnx /root]# grep -i serverurl /etc/sysconfig/rhn/up2date
useNoSSLForPackages[comment]=Use the noSSLServerURL for package, package list, g
serverURL[comment]=Remote server URL
Accessing the cisco-live channel through the web site does not produce a link
for downloading the package. This is probably a seperate problem.
Did you register the machine recently? Remember you migrated from the beta
environment to the live environment, the registration data didn't transfer.
sounds like the box isnt properly registered.
Where was the box registered?
The machine was registered over 20 times, using the proxy server, on Friday
(after beta migration).
Should I understand that #58839 has to be closed? I thought you're still
trying to register the system, that bug is in NEEDINFO.
I suspect this can be closed. But I can't see #58839 to be sure.
Bug 58839 has been closed, and a test of this bug shows no problems. Looks like
the system wasn't properly registered, (it was looking for a certificate on an