RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 821760 - incomprehensible rhn_register UI
Summary: incomprehensible rhn_register UI
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: rhn-client-tools
Version: 6.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Milan Zázrivec
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-15 13:52 UTC by Karel Volný
Modified: 2012-09-18 08:25 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-14 11:06:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
screenshot of the problem (59.62 KB, image/png)
2012-05-15 13:52 UTC, Karel Volný
no flags Details

Description Karel Volný 2012-05-15 13:52:56 UTC
Created attachment 584672 [details]
screenshot of the problem

Description of problem:
Trying to register my system to RHN, I got some strange errors about needing SSL certificate. In the end, I have found that I've just entered wrong address, following the schema outlined by the dialogue box ...

Version-Release number of selected component (if applicable):
rhn-setup-1.0.0-87.el6.noarch


Please see the attached screenshot.

It says "You may connect your system to Red Hat Network (https://rhn.redhat.com/) or ..." - note the "https://rhn.redhat.com/" form of the URL

It also says "Example: https://satellite.example.com"

Yet when I've used the URL in form "https://rhn.on.my.server" it hasn't worked and I got a message about needing to provide correct SSL certificate.

After providing the URL in the same form as the value of serverURL in /etc/sysconfig/rhn/up2date , i.e. "https://xmlrpc.rhn.on.my.server/XMLRPC", it just magically worked.

This is pretty confusing.

Also the error message doesn't help - at first, I've tried to remove "s" from https, trying unsecured connection ... yet I still got a message about wrong SSL certificate! - How is that possible to have wrong certificate when SSL should not be involved at all?

It'd be more helpful to report something like that the XMLRPC interface could not have been reached (not found) instead of asking for SSL certificate when none is needed.

Comment 4 Milan Zázrivec 2012-09-14 11:06:07 UTC
Terribly sorry, but I'm not able to reproduce any of the issues mentioned
in the opening comment.

When I enter

    https://xmlrpc.rhn.errata.stage.redhat.com

into the dialog box, rhn_register nicely appends '/XMLRPC' to it.

When I enter

    https://xmlrpc.rhn.errata.stage.redhat.com/XMLRPC

into the dialog box, rhn_register proceeds nicely without appending anything.

When I use SSL and do not have the valid CA certificate in place, rhn_register
asks me for correct certificate.

When I use http://... schema, rhn_register does not ask for any certificate
at all.

This is all with rhn-client-tools-1.0.0-87.el6.

I'm closing this with worksforme, you're welcome to re-open with an explanation,
should you disagree.

Thanks.


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