Bug 1274391

Summary:	[RFE] add filtering capability to container images in content views
Product:	Red Hat Satellite	Reporter:	Dirk Herrmann <dherrman>
Component:	Container Management - Content	Assignee:	Tom McKay <tomckay>
Status:	CLOSED ERRATA	QA Contact:	Peter Ondrejka <pondrejk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	Unspecified	CC:	bbuckingham, jcallaha, jyejare, mhulan, paji, sgraessl, tomckay, walden
Target Milestone:	Unspecified	Keywords:	FutureFeature, Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-02-21 16:54:37 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 Dirk Herrmann 2015-10-22 15:54:13 UTC

Description of problem:

Satellite users can use filters to customize content that only particular versions are made available to hosts. While for Puppet modules we only allow to have one particular version inside a CV we can use filters for RPM repositories to limit the availability of particular versions of the same RPM. For containers there are currently no filters at all. While publishing a content view all image layers and versions which are inside a repository at this point of time become part of this content view.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

Currently while adding repositories containing container images you can not add filter rules based on image IDs, tags or errata.


Expected results:

While adding repositories containing container images you should be able to add filter rules based on image IDs, tags or errata.

Additional info:

Comment 2 Tom McKay 2017-01-26 13:34:01 UTC

Connecting redmine issue http://projects.theforeman.org/issues/17293 from this bug

Comment 3 Walden Raines 2017-08-16 14:47:03 UTC

I don't have ssh access to the machine I attempted to verify this on so I cannot provide a trace but I do get an error when attempting to verify on 6.3.0.

If I try to create a filter there is a 500 returned from the autocomplete call.  The request looks like this:

GET https://[redacted]/katello/api/v2/docker_tags/auto_complete_name?repoids%5B%5D=4&repoids%5B%5D=5&repoids%5B%5D=6&repoids%5B%5D=7&term=enshift3%2Fcontainer-engine

Query strings:

repoids[]:4
repoids[]:5
repoids[]:6
repoids[]:7
term:openshift3/container-engine

Response:

{
	"displayMessage": "ERROR:  missing FROM-clause entry for table \"katello_docker_tags\"\nLINE 1: ...atello_repositories\".\"id\" IN (4, 5, 6, 7)))) AND (katello_do...\n                                                             ^\n",
	"errors": ["ERROR:  missing FROM-clause entry for table \"katello_docker_tags\"\nLINE 1: ...atello_repositories\".\"id\" IN (4, 5, 6, 7)))) AND (katello_do...\n                                                             ^\n"]
}

I am able to create the filter but it doesn't seem to actually filter anything.  I am not sure if this could be due to the name being incorrect since I cannot autocomplete it.

I'm going to reopen this RFE and am requesting additional information from Tom.

Comment 5 Satellite Program 2017-10-09 18:29:56 UTC

Upstream bug assigned to tomckay

Comment 6 Tom McKay 2017-11-07 22:46:54 UTC

This should go back to ON_QA with the "comment 3" bz fixed in https://bugzilla.redhat.com/show_bug.cgi?id=1506865 (separate issue and unrelated to this original bz and fix)

Comment 9 Satellite Program 2017-12-11 15:23:55 UTC

Upstream bug assigned to tomckay

Comment 11 Tom McKay 2018-01-04 13:47:13 UTC

Moving back to ON_QA since other BZ has been VERIFIED

Comment 12 Peter Ondrejka 2018-01-11 11:06:27 UTC

Verified on Sat 6.3 snap 30, docker tag filters can now be applied to content views.

Comment 13 Satellite Program 2018-02-21 16:54:37 UTC

Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA.
> > 
> > For information on the advisory, and where to find the updated files, follow the link below.
> > 
> > If the solution does not work for you, open a new bug report.
> > 
> > https://access.redhat.com/errata/RHSA-2018:0336