Red Hat Bugzilla – Bug 253031
back button in tui of rhn_register causes Invalid ORG_ID requested error
Last modified: 2008-05-21 12:50:58 EDT
While testing bug #233067 we found the following scenario
would cause the Invalid ORG_ID error.
1. rhn_register tui
2. On the login screen use and existing user/password.
3. Click next.
4. Click back on this screen.
5. enter a different login and click next.
Observe the error.
[root@rlx-3-08 ~]# rhn_register
An error has occurred:
Error Class Code: 42
Error Class Info: Invalid ORG_ID requested
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.
See /var/log/up2date for more information
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
User email@example.com's account has been closed
fixed in rev 134551.
The "Back" button is now greyed out so I cannot go back as the original comment
says. Is that the fix for this?
I'm trying to test this, but I don't see the back button grayed out. Cameron,
what version where you using?
i think this is on qa?
Sure it was. I switched purposely to NEEDINFO to get more information from
Cameron who has tested the bug, since I'm getting different testing results.
I did not have luck with reproducing this with old version from RHEL-5.0
(rhn-client-tools-0.4.13-1.el5) nor one from 5.1, guess something changed on the
server side but that's not that important.
I do this scenarios with latest revision 0.4.17-8:
login in TUI app via my personal account and pass to RHN, I see screen that I
have no active subscription, which is OK, I hit back, issue QE login, with
unlimited amount of subscriptions and hit next, it logs me into, but I got the
"no active subscription" again.
Justin, is this the reported bug, or is it a new one?
Doing this in reverse order, QE credentials and then personal one gives me
expected results, of no no active subscription.
hrm, that seems to be a new bug actually...
opened up bz 442930 and proposed for 5.3 as it does not seem to be a blocker.
Jesus, do you know what version of rhn-client-tools was the affected? When did
you seen it reproducible last time?
I believe the reason you weren't able to reproduce is because EUS was not
enabled on the server. With the version of rhn-client-tools released with RHEL
5.1 you see the issue if you were connecting to hosted when it did not have EUS
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.