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.
Description of problem:
Errata and packages reports as promoted when trying to repromote to a different env (UI).
Version-Release number of selected component (if applicable):
Beta2
katello-0.1.300-1.el6.noarch
katello-cli-0.1.100-2.el6.noarch
katello-agent-0.15-1.el6.noarch
pulp-0.0.267-2.el6.noarch
candlepin-0.5.22-1.el6.noarch
subscription-manager-0.96.17-1.el6.x86_64
python-rhsm-0.96.15-1.el6.noarch
yum-3.2.29-22.el6.noarch
How reproducible:
Fresh install.
Steps to Reproduce:
1. Sync fake-cdn or some products from CDN.
2. Create two environments env1 and env2.
3. Promote a product with errata and/or packages to env1.
4. Create new changeset for Library->env2 promotion.
5. Try to find errata or package - there is no +Add button there.
Actual results:
All I can promote is a whole product.
Expected results:
I should be able to promote an errata to env1 AND to env2.
So i did find an issue with the above scenario, but i think it broke after this bug was filed:
e85b2c745094f576c128388f01429814aec9e6a7
In the above scenario it appears that you never promoted the product to env2, this results in the add/remove links not showing up for errata or package as the product is not in the next environment. You always have to promote the product before individual items are eligible for promotion.
Going to move this to modified, but lzap, could you confirm that you did not promote the product to env 2?
See step 4- he means two different paths. If you promote to path1, it's marked "Promoted" in library and you cannot promote it down the other path anymore.