Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1220556

Summary:

Content View Promote Fails with Katello::Errors::CandlepinError

Product:

Red Hat Satellite

Reporter:

Mike McCune <mmccune>

Component:

Content Management

Assignee:

Partha Aji <paji>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Tazim Kolhar <tkolhar>

Severity:

high

Docs Contact:

Priority:

unspecified

Version:

6.1.0

CC:

bkearney, cwelton, tkolhar

Target Milestone:

Unspecified

Keywords:

Triaged

Target Release:

Unused

Hardware:

Unspecified

OS:

Unspecified

URL:

http://projects.theforeman.org/issues/10697

Whiteboard:

Fixed In Version:

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2015-08-12 13:59:27 UTC

Type:

Bug

Regression:

---

Mount Type:

---

Documentation:

---

CRM:

Verified Versions:

Category:

---

oVirt Team:

---

RHEL 7.3 requirements from Atomic Host:

Cloudforms Team:

---

Target Upstream Version:

Embargoed:

Attachments:

Description	Flags
content view	none

Description Mike McCune 2015-05-11 20:05:15 UTC

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

Comment 3 Partha Aji 2015-06-03 21:25:55 UTC

Created redmine issue http://projects.theforeman.org/issues/10697 from this bug

Comment 4 Partha Aji 2015-06-03 21:56:35 UTC

Should be fixed when https://github.com/Katello/katello/pull/5271 gets merged

Comment 5 Bryan Kearney 2015-06-05 16:06:39 UTC

Moving to POST since upstream bug http://projects.theforeman.org/issues/10697 has been closed
-------------
Partha Aji
Applied in changeset commit:katello|c2aa177c3ae76a02bfaa1071a65628e32e332626.

Comment 8 Tazim Kolhar 2015-06-12 09:33:14 UTC

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:

Comment 9 Tazim Kolhar 2015-06-12 09:33:42 UTC

Created attachment 1037969 [details]
content view

Comment 10 Bryan Kearney 2015-08-11 13:24:45 UTC

This bug is slated to be released with Satellite 6.1.

Comment 11 Bryan Kearney 2015-08-12 13:59:27 UTC

This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015.