Bug 444971 - reactivation key can be used to register rhel5 systems to rhel 4 channels
Summary: reactivation key can be used to register rhel5 systems to rhel 4 channels
Keywords:
Status: CLOSED DUPLICATE of bug 428699
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Registration
Version: 510
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Justin Sherrill
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-02 14:17 UTC by Preethi Thomas
Modified: 2008-09-30 14:29 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-09-30 14:29:32 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Preethi Thomas 2008-05-02 14:17:17 UTC 
Description of problem:
reactivation key can be used to register rhel5 systems  to rhel4 channels.

Version-Release number of selected component (if applicable):

rhn-satellite-5.1.0-181-redhat-linux-as-i386-4-teng.iso

How reproducible:
always

Steps to Reproduce:
1. register 2 systems (rhel4 & rhel5)(system1 & system2) and give provisioning
entitlements.
2 create reactivation keys for both the systems.
3. reactivate system1 (rhel4) with the reactivation key of system2 (rhel5).
  
Actual results:
reactivation key can be used to register rhel5 systems to rhel4 channels


Expected results:


Additional info:
Comment 1 Preethi Thomas 2008-05-02 14:45:37 UTC 
on further investigation I noticed that the system profile name remains that of
the rhel5 system of which the reactivation key was used. but the host name/ip
address is of the rhel4 system which I registered using the reactivation key.
Comment 2 Brandon Perkins 2008-09-30 14:29:32 UTC 

*** This bug has been marked as a duplicate of bug 428699 ***
Note You need to log in before you can comment on or make changes to this bug.