Bug 796573

Summary:	Errata and packages reports as promoted when trying to repromote to a different env (UI)
Product:	Red Hat Satellite	Reporter:	Lukas Zapletal <lzap>
Component:	WebUI	Assignee:	Justin Sherrill <jsherril>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Garik Khachikyan <gkhachik>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0.0	CC:	cwelton, gkhachik, mkoci, mmccune
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-08-22 18:28:56 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Lukas Zapletal 2012-02-23 08:37:58 UTC

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.

Comment 1 Justin Sherrill 2012-02-27 22:08:23 UTC

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?

Comment 3 Mike McCune 2012-03-07 23:43:19 UTC

mass move ON_QA after brewing

Comment 4 Corey Welton 2012-03-15 18:03:20 UTC

This bz is confusing. Does different environment mean different path, i.e., Library -> Dev1 and Library -> Dev2?

Comment 5 Jeff Weiss 2012-03-21 01:51:07 UTC

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.

Comment 6 Jeff Weiss 2012-03-21 01:54:27 UTC

I am finding that once you promote the product, the Errata show as Promoted and cannot be promoted separately.  Will investigate further.

Comment 7 Jeff Weiss 2012-03-21 01:56:29 UTC

Oh right, you only get one shot at testing promotion of errata unless you have repos that get new errata, which I don't :)