Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1694717 - Not able to schedule errata via Host Collections with following string "type = security and not ( title ~ *kernel* )" which used to work in Satellite 6.2
Summary: Not able to schedule errata via Host Collections with following string "type ...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Errata Management
Version: 6.3.0
Hardware: All
OS: All
unspecified
medium vote
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Perry Gagne
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-01 13:13 UTC by raju kumar
Modified: 2019-04-02 17:20 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description raju kumar 2019-04-01 13:13:48 UTC
Description of problem:

Not able to schedule errata via Host Collections with the following string "type = security and not ( title ~ *kernel* )" which worked in Satellite 6.2

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

Red Hat Satellite 6.3

How reproducible:

Always

Steps to Reproduce:

1. Login to Red Hat Satellite WebUi --> "Hosts" --> "Hosts Collection" --> 
"Errata Installation" --> In the Search  bar  --> "type = security and not ( title ~ *kernel* )"

2. Earlier it used to give the desired output in satellite 6.2 but doesn't work in satellite 6.3.

Actual results:

It is not giving any results at all. The result is completely blank.

Expected results:

It should give a list of all security errata by excluding kernel ones.

Additional info:

We do have this article [1] which has described this issue but partially.

- 1. https://access.redhat.com/solutions/3498161


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