Bug 453757 – rhn_register doesn't accept http satellite address without SSL certificate in place

This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes

Bug 453757 - rhn_register doesn't accept http satellite address without SSL certificate in place

Summary:	rhn_register doesn't accept http satellite address without SSL certificate in...

Status:	CLOSED INSUFFICIENT_DATA

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	Registration (Show other bugs)
Sub Component:
Version:	510
Hardware:	i386 Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Justin Sherrill
QA Contact:	Brandon Perkins
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-07-02 08:33 EDT by Martin Sivák
Modified:	2009-02-10 13:33 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2009-02-10 13:33:12 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Martin Sivák 2008-07-02 08:33:20 EDT

Description of problem:

When trying to register new instalation of RHEL 5 Server on stage-prod.brq
internal satellite, the correct HTTP address was refused. After downloading the
RHN-ORG-TRUSTED-SSL-CERT and puting it into /usr/share/rhn, it suddenly started
to work.

Version-Release number of selected component (if applicable):
RHN Satellite version 510
Red Hat Network Client Tools 0.4.17-8.el5
 
How reproducible:
install clean RHEL5 Server
run rhn_register, try to add http://sputnik-prod/XMLRPC as RHN Satellite address 


Actual results:
Error message with "This should not happen.."

Expected results:
RHN registration completed successfully

Comment 1 Brandon Perkins 2008-12-23 11:48:29 EST

We cannot reproduce this behavior.  Can you please send along the exact configuration files and command-line interaction that was used to get into this state?

Comment 2 Brandon Perkins 2009-02-10 13:33:12 EST

Closed due to inactivity.

Note You need to log in before you can comment on or make changes to this bug.