Bug 1402826

Summary:	It's possible to add the same package for content-view's package filter twice
Product:	Red Hat Satellite	Reporter:	Andrii Balakhtar <abalakht>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	6.2.5	CC:	bbuckingham, jcallaha, oshtaier
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-05 00:14:58 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:

Description Andrii Balakhtar 2016-12-08 12:30:25 UTC

Description of problem:
It's possible to add the same package for content-view's package filter twice on 6.2.z. On Sat 6.3 error is correctly thrown

Version-Release number of selected component (if applicable):
Sat 6.2.5 Snap 3.0

How reproducible:
Always

Steps to Reproduce:
1. Create a CV, add a repo with some packages
2. Create exclusive or inclusive package filter for mentioned CV.
3. Add any package to filter, e.g. package name 'walrus', version 'Equal To' '0.71-1'.
4. Repeat step 3 once again

Actual results:
Same package with same version was successfully added.

Expected results:
Package of the same version shouldn't be added once again, proper error message should be shown, like on sat 6.3.

Additional info:

Comment 2 Brad Buckingham 2017-01-05 00:14:58 UTC


*** This bug has been marked as a duplicate of bug 981639 ***

Comment 3 Andrii Balakhtar 2017-02-17 13:04:17 UTC

Brad, are you sure that's correct resolution? I was aware of BZ981639, but it's for 6.3 . This BZ was pointing that the problem exists in 6.2.z branch too, sorry for misleading description. If it's not going to be fixed in 6.2.z - then WONTFIX is probably better resolution here.
I'm asking as our automation correctly skips WONTFIXes for specific branches but not duplicates (original issue is closed -> the test becomes unblocked -> it's failing as the fix is not there in 6.2.z).

Comment 4 Andrii Balakhtar 2017-03-23 14:17:28 UTC

Changing resolution to 'WONTFIX' as it seems as more relevant resolution to me which also works perfectly with our automation. If you think this is wrong, please feel free to update it.