Bug 1379672 - hammer content-view-filter create does not support Date and Type
Summary: hammer content-view-filter create does not support Date and Type
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.2.2
Hardware: Unspecified
OS: Unspecified
medium
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-27 12:19 UTC by Sebastian Hetze
Modified: 2017-04-25 16:09 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-27 19:39:14 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.