Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 643225

Summary:	Machines are still subscribed to their previous group & activation keys after re-provisioning, even if they are not in the new kickstart
Product:	Red Hat Satellite 5	Reporter:	Marcelo Moreira de Mello <mmello>
Component:	Provisioning	Assignee:	Tomas Lestach <tlestach>
Status:	CLOSED DEFERRED	QA Contact:	Red Hat Satellite QA List <satqe-list>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	530	CC:	cperry, mmello
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:	2011-04-27 13:08:30 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:	462714

Description Marcelo Moreira de Mello 2010-10-14 23:38:20 UTC

Description of problem:

Machines are still subscribed to their previous group & activation keys after re-provisioning, even if they are not in the new kickstart. 


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

How reproducible:
100%

Steps to Reproduce:

1- create 2 kickstarts, 2 keys, 2 groups ; each kickstart should use 1 key and 1 group

2- kickstart a system with kickstart1

3- re-provision the system with kickstart2
  
Actual results:
The machine is associated with all groups and all keys

Expected results:

Add a kickstart option to cause the removal of all activation keys if the kickstart is used in re-provisioning or change the general behaviour of satellite when re-provisioning.

Additional info: