Bug 1198297

Summary: If multiple activation keys used, and one has config file deploy enabled, then all activation keys configs get deployed
Product: Red Hat Satellite 5 Reporter: Michele Newman <mbutterfly23>
Component: RegistrationAssignee: Matej Kollar <mkollar>
Status: CLOSED NOTABUG QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 570CC: cperry, jlyle
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-04 14:33:03 UTC Type: Bug
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 Michele Newman 2015-03-03 18:14:40 UTC 
Description of problem:
If multiple activation keys are being used to register a system, and one has config file deploy enabled, then all activation keys configs get deployed.

Version-Release number of selected component (if applicable):
Satellite 5.4 on up.  Haven't tested previous satellite versions.

How reproducible:
Every time.

Steps to Reproduce:
1. Create multiple activation keys, with config files
2. Enable config file deploy on one
3. Register a system (in kickstart or bootstrap)
 

Actual results:
All configs in all activation keys get deployed

Expected results:
Registration should honor which activation keys have config file deployment enabled.  

Additional info:
Sometimes its best not to deploy all config files especially when bootstrapping existing systems and it could potentially break the system.    

Found where this was initially made to deploy all configs: https://bugzilla.redhat.com/show_bug.cgi?id=557581#c3