Bug 209174

Summary: Issues with Activation Keys and Kickstarts
Product: [Retired] Red Hat Network Reporter: John Wregglesworth <wregglej>
Component: RHN/BackendAssignee: Mike McCune <mmccune>
Status: CLOSED WORKSFORME QA Contact: Brandon Perkins <bperkins>
Severity: medium Docs Contact:
Priority: medium    
Version: rhn500-satellite-betaCC: rhn-bugs
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: 2006-11-07 19:44:19 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: 210004    
Bug Blocks: 189917    

Description John Wregglesworth 2006-10-03 18:57:14 UTC 
Description of problem: If you kickstart a machine with a kickstart profile that
has an activation key associated with it, the config files associated with the
key do not get deployed and the child channel set up in the key do not get
subscribed to.


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


How reproducible: Always


Steps to Reproduce:
1. If necessary, create a configuration channel.
2. Create a file in the configuration.
3. Have the file get deployed upon registration
4. Create an activation key.
5. Have the activation key subscribe the client using it to multiple channels.
6. Associate the configuration channel with the activation key.
7. Associate the activation key with a kickstart profile.
8. Kickstart a machine with the kickstart profile. The packages will get
installed, but the config file doesn't get deployed and the channels set up in
the activation key aren't subscribed to.
Comment 1 Pete Vetere 2006-10-09 15:33:03 UTC 
This seems to affect guests only.
Comment 2 Pete Vetere 2006-10-09 17:21:46 UTC 
Can't repro this bug until 210004 is fixed.