This is the scenario that I saw the error, may be more ways to reproduce this: 1) Create a lifecycle env beyond Library 2) Create a content view 3) add a few yum repos to CV 4) Publish CV 5) Promote CV to next env 6) remove yum repos from CV 7) add different yum repos to CV 8) Publish new version of CV 9) Attempt to promote CV, receive task error: "Exception: Katello::Errors::CandlepinError: The content with id 1431366478942 has already been promoted in this environment." This comes from Candlepin: https://github.com/candlepin/candlepin/blob/master/server/src/main/java/org/candlepin/resource/EnvironmentResource.java#L183
Created redmine issue http://projects.theforeman.org/issues/10697 from this bug
Should be fixed when https://github.com/Katello/katello/pull/5271 gets merged
Moving to POST since upstream bug http://projects.theforeman.org/issues/10697 has been closed ------------- Partha Aji Applied in changeset commit:katello|c2aa177c3ae76a02bfaa1071a65628e32e332626.
VERIFIED: # rpm -qa | grep foreman ruby193-rubygem-foreman_discovery-2.0.0.15-1.el7sat.noarch foreman-libvirt-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.14-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.10-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch foreman-compute-1.7.2.27-1.el7sat.noarch foreman-gce-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman-redhat_access-0.2.0-8.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.14-1.el7sat.noarch foreman-debug-1.7.2.27-1.el7sat.noarch foreman-vmware-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.8-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch rubygem-hammer_cli_foreman_docker-0.0.3.7-1.el7sat.noarch foreman-proxy-1.7.2.5-1.el7sat.noarch dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.13-1.el7sat.noarch dell-pe1955-02.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-ovirt-1.7.2.27-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.7-1.el7sat.noarch foreman-1.7.2.27-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch foreman-postgresql-1.7.2.27-1.el7sat.noarch steps: 1) Create a lifecycle env beyond Library 2) Create a content view 3) add a few yum repos to CV 4) Publish CV 5) Promote CV to next env 6) remove yum repos from CV 7) add different yum repos to CV 8) Publish new version of CV 9) Attempt to promote CV, receive task error:
Created attachment 1037969 [details] content view
This bug is slated to be released with Satellite 6.1.
This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.