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.

Description of problem:

When trying to promote a content view to a 2nd promotion path (DEV2 for example), a view will show up as 'promoted' if it has been promoted to another path (Dev1).



How reproducible:
Always

Steps to Reproduce:
1.  Create an environment Library->Dev1
2.  Create an environment Library->Dev2
3.  Create a content view definition and publish it to "TestView"
4.  Promote TestView to Dev1 via the UI
5.  Attempt to promote TestView to Dev2 via the UI

Actual results:
UI says that the view has already been promoted and does not allow promotion

Expected results:
UI does not allow promotion, says its already been promoted

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

I just ran a few tests with katello master and it appears that this may have already been solved.  I had the 3 environment paths below and was able to successfully promote the same content view to each.

Library->dev
Library->dev2
Library->dev3

please check following scenario as well:

Library -> env-dev 
Library -> env-test
1. create CV1 and promote to env-dev
2. create CV2 and try to create a changeset to *promote* the *same* enviuronment - UI just shows up all the time with deletion type of the changeset :/

We are indeed able to promote same CV's to multiple promotion paths.

Satellite-6.0.2-RHEL-6-20131016.0

*** Bug 968421 has been marked as a duplicate of this bug. ***

This was verified and delivered with MDP2. Closing it out.

This was delivered and verified with MDP2. Closing the bug.