Description of problem:
When kickstarting new RHEL 5.5 servers, all configuration files available via configuration channels configured for use in related activation keys are being deployed upon registration of the OS during kickstart.

I have validated that the related activation keys are NOT configured to deploy all config files upon activation, yet it happens regardless.

Version-Release number of selected component (if applicable):
This is seemingly new as of v1.0 ... this was not an issue with v0.8.

How reproducible:
Every time.

Steps to Reproduce:
1.  Create kickstart profile and select activation key.
2.  Ensure activation key is not set to deploy all config files upon activation.
3.  Kickstart server and note unwanted configuration files.
  
Actual results:
In my case, I have certain files related to network configuration that should only be deployed based on logic in the post-install script.  However, by monitoring the installation process, I can see that these files are being deployed as soon as the system is registered... before my non-chroot post-install script runs.

Expected results:
Logic within my post-install script only pulls the offending files in the correct hardware scenario.

Additional info: