Bug 987470

Description of problem:
When we create deletion type changeset on some environment, and add into it content view which was already promoted, and try to promote that changeset, it will fail.

Version-Release number of selected component (if applicable):
katello-cli-1.4.2-1.git.131.cacfdea.el6.noarch
Katello-Katello-Installation-RegisterRHNClassic-1.1-4.noarch
katello-configure-1.4.3-1.git.67.f71e590.el6.noarch
elasticsearch-0.19.9-7.el6.noarch
katello-glue-elasticsearch-1.4.2-1.git.951.091dd45.el6.noarch
katello-all-1.4.2-1.git.951.091dd45.el6.noarch
Katello-Katello-Configuration-KatelloClient-1.1-50.noarch
openldap-2.4.23-31.el6.x86_64
python-ldap-2.3.10-1.el6.x86_64
Katello-Katello-Installation-ConfigureRepos-1.7-3.noarch
katello-repos-1.4.2-1.el6.noarch
ruby193-rubygem-net-ldap-0.3.1-1.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
pulp-rpm-handlers-2.1.2-0.3.beta.el6.noarch
ruby193-rubygem-ldap_fluff-0.2.2-1.el6.noarch
katello-cli-common-1.4.2-1.git.131.cacfdea.el6.noarch
pulp-selinux-2.1.2-0.3.beta.el6.noarch
katello-certs-tools-1.4.2-1.el6.noarch
pulp-rpm-plugins-2.1.2-0.3.beta.el6.noarch
signo-katello-0.0.9-1.el6.noarch
katello-selinux-1.4.3-1.git.4.99dc194.el6.noarch
katello-glue-pulp-1.4.2-1.git.951.091dd45.el6.noarch
katello-1.4.2-1.git.951.091dd45.el6.noarch
candlepin-0.8.17-1.el6.noarch
candlepin-tomcat6-0.8.17-1.el6.noarch
katello-agent-1.4.3-1.git.1.24fe511.el6.noarch
signo-0.0.9-1.el6.noarch
apr-util-ldap-1.3.9-3.el6_0.1.x86_64
Katello-Katello-Installation-KatelloNightly-1.0-13.noarch
pulp-server-2.1.2-0.3.beta.el6.noarch
katello-common-1.4.2-1.git.951.091dd45.el6.noarch
katello-glue-candlepin-1.4.2-1.git.951.091dd45.el6.noarch
candlepin-selinux-0.8.17-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
candlepin-cert-consumer-cfseserver2.usersys.redhat.com-1.0-1.noarch
Katello-Katello-Sanity-ImportKeys-1.2-1.noarch

How reproducible:
always

Steps to Reproduce:
1. Create 2 environments "Dev" (prior=Library) and "Test"(prior=Dev), zoo repo, sync it.
2. Create content definition and add zoo repo into it. Create some filter with rule to include some package (or errata)  for example "lion" and publish and promote content view to Dev environment.
3. Promote the same content view to Test environment as well.
4. Create deletion type changeset on Test environment. Add content view into it.
5. Apply changest, and you will see that it shows error "promotion failed", which is bug

Actual results:
error is shown that "promotion failed".

Expected results:
no error should be shown as content view was already promoted to that environment, so deletion will be ok

Additional info:
the same problem when in content view filter we have errata instead of package