Bug 498275
Summary: | obtainReactivationKey doesnt update key in webui and old key is not replaced | ||
---|---|---|---|
Product: | Red Hat Satellite 5 | Reporter: | Sayli Karmarkar <skarmark> |
Component: | API | Assignee: | Brad Buckingham <bbuckingham> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Sayli Karmarkar <skarmark> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 530 | CC: | cperry, mmraka |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | sat530 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-09-10 19:55:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 456996 |
Description
Sayli Karmarkar
2009-04-29 17:33:03 UTC
master git commit: 8fa2b65fedf786fc8841633cd456a3f4131acaa6 vader git commit: 66b40db71571aca6acb98d604c580267f4e91fb0 After investigation, the issue was that the API was creating a new reactivation key but not removing any existing ones when invoking the API. Updated the API to remove the existing and create a new. verified. Validated in stage -> RELEASE_PENDING. #1 - Reactivation key is always shown in webUI and works. #2 - Old key is no longer valid. rhnreg_ks --serverUrl=http://dell-pem710-01.rhts.eng.bos.redhat.com/XMLRPC --activationkey=re-1-fbdd7c94eaefbadf3c238591852cd264 --force Error Message: Could not find token 're-1-fbdd7c94eaefbadf3c238591852cd264' Error Class Code: 60 Error Class Info: The activation token specified could not be found on the server. Please retry with a valid key. 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 therefore 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. http://rhn.redhat.com/errata/RHEA-2009-1434.html |