Bug 515810
| Summary: | error registering with activation keys | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite 5 | Reporter: | Xixi <xdmoon> | ||||
| Component: | Server | Assignee: | Pradeep Kilambi <pkilambi> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jeff Browning <jbrownin> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 520 | CC: | cperry, jsefler, mmraka | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | sat530 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | 480080 | Environment: | |||||
| Last Closed: | 2009-09-10 20:38:56 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: | 480080 | ||||||
| Bug Blocks: | 456985 | ||||||
| Attachments: |
|
||||||
|
Description
Xixi
2009-08-05 19:41:48 UTC
Created attachment 356417 [details]
sat 5.2.0 patch from spacewalk fix
*For Engineering*: Customer reported issue on Sat 5.2.0 and the patch fixed it, this BZ is just for tracking and to make sure it's QA'd for Sat 5.3.0. Thanks! Fixed since Space04 apparently. Moving straight to ON_QA. Verified (Satellite-5.3.0-RHEL5-re20090724.0) with updates dated Aug 6 After scheduling a kickstart as describe in the problem and going to the Reactivation tab, I am presented with the following red message in the Satellite GUI: There is a kickstart session in progress for this system. Modifying this activation key is likely to cause the system to fail to re-register when the kickstart session is complete. Using this key manually could cause unintended side-effects. ID: 416 Org ID: 62 Key: re-62-c3c70c1af5bafc6166cd0110197394f0 [root@fjs-0-12 ~]# rhnreg_ks --serverUrl=http://dhcp77-153.rhndev.redhat.com/XMLRPC --force --activationkey=re-62-c3c70c1af5bafc6166cd0110197394f0 [root@fjs-0-12 ~]# Using the key that was inherently generated by scheduling a kickstart, I was successfully able to use it with rhnreg_ks at the command line. After rhnreg_ks was successfully executed, I went to the system's Reactivation tab and found that the key was no longer there. All looks good. No error encountered as described in the problem description. Moving to VERIFIED Verified in stage -> RELEASE_PENDING. * scheduled kickstart for client * generated reactivation key - page showed warning: There is a kickstart session in progress for this system. Modifying this activation key is likely to cause the system to fail to re-register when the kickstart session is complete. Using this key manually could cause unintended side-effects. ID: 3944 Org ID: 36 Key: f808922b3b4bdb62afc8b1f685ed70ac * registered client using the key above with no error * after reactivation key page reload key dissappeared * Event -> History on client shows (n/a) Reactivation via Token 08/14/09 6:28:42 AM EDT (n/a) Kickstart session canceled 08/14/09 6:28:42 AM EDT failed Initiate a kickstart scheduled by mmraka 08/14/09 6:28:42 AM EDT 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 |