Red Hat Bugzilla – Bug 470120
registration number validation fails when calling registration.new_system server call
Last modified: 2013-01-10 04:22:08 EST
Description of problem: When client passes the registrationNumber through s.registration.new_system to hosted, it works the first time but fails in subsequent attempts. Apparently this was new code thats not working appropriately. How reproducible: always Steps to Reproduce: 1. Register a RHEL-5.3 client to rhn.redhat.com with a --subscription option 2. the command fails with: Error Message: Attempt to register a system failed Error Class Code: 16 Error Class Info: Invalid product registration code. Explanation: 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. Actual results: does'nt validate IN Expected results: should validate IN correctly
http://wwwapps.rdu.redhat.com:8080/xplanner/do/view/userstory?oid=59467
Prad, rather than fixing the code server side, would you accept a patch to rhnreg_ks to have it follow the same code path as rhn_register? (ie call activate_hardware_info and new_system_user_pass)?
hi James: Jus thought it would be cleaner to fix it on the server so we don't have to fix multiple client versions. but if you prefer a fix on the client few questions: * if we go with new_system_user_pass would it work in conjunction with activation key? or do we have make user/passwd mandatory with --subscription option. * will we be defaulting to registration_number instead of registrationNumber? so is the older version still available on the server or do you guys need to revert something for that? * also we'll have to fix this for RHEL-4 as well? which is 4.8 so the fix wont go in for that until mid next year.. I'm ok with either client or server which ever you prefer, as long as it works with existing scenarios. Thanks, ~ Prad
Ah, good point about the activation key. So let's keep the fix server-side. This is going to be a bit more involved than I first thought, however, since registration.new_system is called by rhn_register in rhel 4 and lower, and you can provide one of the old style subscription numbers. We'll need to ensure that whatever changes are made don't break that
all set on dev