Bug 966280

Description of problem:

Every time I refresh and promote a published content view, a new entry seems to be added to candlepin as an available environment to my client. Having refreshed and promoted my view three times, here's what subscription-manager shows:

# subscription-manager environments --org Org1 --user admin --password admin | grep ^Name | sort
Name:                 	DEV                      
Name:                 	DEV/PublishedAgent       
Name:                 	DEV/PublishedChrome64    
Name:                 	DEV/PublishedChrome64    
Name:                 	DEV/PublishedChrome64    
Name:                 	Library/PublishedAgent   
Name:                 	Library/PublishedChrome64

Note how DEV/PublishedChrome64 is returned 3 times. Apparently 

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

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.8.7-1.el6_4.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.8.7-1.el6_4.noarch
* candlepin-tomcat6-0.8.7-1.el6_4.noarch
* elasticsearch-0.19.9-8.el6sat.noarch
* foreman-1.1.10002-29.noarch
* foreman-postgresql-1.1.10002-29.noarch
* katello-1.4.2-6.el6sat.noarch
* katello-all-1.4.2-6.el6sat.noarch
* katello-candlepin-cert-key-pair-1.0-1.noarch
* katello-certs-tools-1.4.2-2.el6sat.noarch
* katello-cli-1.4.2-5.el6sat.noarch
* katello-cli-common-1.4.2-5.el6sat.noarch
* katello-common-1.4.2-6.el6sat.noarch
* katello-configure-1.4.3-9.el6sat.noarch
* katello-configure-foreman-1.4.3-9.el6sat.noarch
* katello-foreman-all-1.4.2-6.el6sat.noarch
* katello-glue-candlepin-1.4.2-6.el6sat.noarch
* katello-glue-elasticsearch-1.4.2-6.el6sat.noarch
* katello-glue-pulp-1.4.2-6.el6sat.noarch
* katello-qpid-broker-key-pair-1.0-1.noarch
* katello-qpid-client-key-pair-1.0-1.noarch
* katello-selinux-1.4.3-3.el6sat.noarch
* openldap-2.4.23-31.el6.x86_64
* openldap-devel-2.4.23-31.el6.x86_64
* pulp-rpm-plugins-2.1.1-1.el6sat.noarch
* pulp-selinux-2.1.1-1.el6sat.noarch
* pulp-server-2.1.1-1.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.1.7-3.el6sat.noarch
* ruby193-rubygem-net-ldap-0.2.2-7.el6_4.noarch
* signo-0.0.10-1.el6sat.noarch
* signo-katello-0.0.10-1.el6sat.noarch

How reproducible:


Steps to Reproduce:
1. Create a content view, add a single repo to it and publish it
2. Promote the published content view
3. Refresh the published view (version 2)
4. Register and subscribe a client against the organization (use an activationkey)
5. In the client run: subscription-manager environments --org <YOUR ORG> --user admin --password admin | grep ^Name | sort

Actual results:

You'll see 2 entries for your published content view

Expected results:


Additional info:

# curl -s -k -u admin:admin https://localhost/subscription/owners/Org1/environments | json_reformat
[
  {
    "id": "9",
    "name": "DEV",
    "description": null
  },
  {
    "id": "8",
    "name": "Library",
    "description": null
  },
  {
    "id": "9-12",
    "name": "DEV/PublishedAgent",
    "description": ""
  },
  {
    "id": "8-12",
    "name": "Library/PublishedAgent",
    "description": ""
  },
  {
    "id": "9-13",
    "name": "DEV/PublishedChrome64",
    "description": ""
  },
  {
    "id": "8-13",
    "name": "Library/PublishedChrome64",
    "description": ""
  },
  {
    "id": "9-13",
    "name": "DEV/PublishedChrome64",
    "description": ""
  },
  {
    "id": "9-13",
    "name": "DEV/PublishedChrome64",
    "description": ""
  }
]