Bug 444971

Summary: reactivation key can be used to register rhel5 systems to rhel 4 channels
Product: Red Hat Satellite 5 Reporter: Preethi Thomas <pthomas>
Component: RegistrationAssignee: Justin Sherrill <jsherril>
Status: CLOSED DUPLICATE QA Contact: Brandon Perkins <bperkins>
Severity: low Docs Contact:
Priority: low    
Version: 510   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-30 14:29:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

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 ***