Description of problem:

   The katello-host-tools has a script in the RPM that triggers a "katello-package-upload" and a "katello-enabled-repos-upload" when the RPM is installed (or uninstalled).

   # rpm -q katello-host-tools --scripts
    posttrans scriptlet (using /bin/sh):
    katello-package-upload 2> /dev/null
    katello-enabled-repos-upload 2> /dev/null
    exit 0


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

   Current

How reproducible:

Steps to Reproduce:
1.  Install katello-host-tools rpm on a large number of Content Hosts

Actual results:

   All Content Hosts will begin uploading package profiles immediately.

Expected results:

   Do not upload package and repo information from plugin until done so by yum or rhsmd.

Additional info:

   I would suspect the RPM install script is there to generate an initial state, as future rhsmd uploads and yum plugin uploads only act when they detect a change.   However, if an initial flag can be set to indicate that it's never uploaded, that could potentially be used as a determination whether the initial state has ever been uploaded to the Satellite/portal.

  The downside in large environments is that an install/upgrade of all the clients can potentially render the Satellite unavailable as it doesn't benefit from any of the random variation introduced by subscription-manager's splay, or the normal stagger of yum activity in the environment.  Instead, it is immediate and overwhelming.