Bug 1379672

Summary:	hammer content-view-filter create does not support Date and Type
Product:	Red Hat Satellite	Reporter:	Sebastian Hetze <shetze>
Component:	Content Views	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2.2	CC:	bbuckingham, ehedgren, jcallaha, juwu
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-10-27 19:39:14 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:

Description Sebastian Hetze 2016-09-27 12:19:47 UTC

Description of problem:

There is no way to create a 'Date and Type' type of content view filter with hammer.

While https://access.redhat.com/solutions/2216781 describes a procedure that may result in something similar, the appearance of the filter in Satellite-6.2 is significantly different from a manually created 'Date and Type' filter.

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

How reproducible:
always

Steps to Reproduce:
1. Create CV RHEL7_Base
2. hammer content-view filter create --organization=$ORG --content-view='RHEL7_Base' --type='erratum' --name='errata1606' --inclusion='false'
3. hammer content-view filter rule create --organization=$ORG --start-date='2016-06-01' --content-view='RHEL7_Base' --content-view-filter='errata1606' --date-type='updated' 

Actual results:
The filter has Content Type 'Errata'
The filter offers a List/Remove tab which is is empty and only allows to add individual errata


Expected results:
The filter should have Content Type 'Errata - Date and Type'
The filter should have a 'Erratum Date Range' tab to enter/modify appropriate dates

Additional info:

Comment 2 Brad Buckingham 2016-10-27 19:39:14 UTC

It is possible to create a the desired filter rule; however, the '--types' field (e.g. --types 'security') must be included as indicated in the KCS from the initial description.

There is a change in the upstream that was submitted for bug 1386688 that will allow that field to default to all types, to be consistent with the UI user experience.