Bug 1300366

Summary:	"any of" / "not any of" not appearing in BRE component picker
Product:	[Community] Bugzilla	Reporter:	Tom Lavigne <tlavigne>
Component:	Internal Tools	Assignee:	Matt Tyson 🤬 <mtyson>
Internal Tools sub component:	Rules Engine	QA Contact:	tools-bugs <tools-bugs>
Status:	CLOSED CURRENTRELEASE	Docs Contact:
Severity:	high
Priority:	high	CC:	huiwang, jkurik, jmcdonal, lmiksik, mtahir, mtyson, qgong
Version:	4.4	Keywords:	Regression
Target Milestone:	4.4
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	4.4.11048.2	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-15 00:57:19 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 Tom Lavigne 2016-01-20 15:04:16 UTC

Description of problem:

There appears to be a regression that is preventing us from updating some of our BRE rules.   Look at this rule:  'RHEL6 !Extras Keyword'

In the "Detail" view of the rule you can see

Component is not any of 'openvswitch', 'preupgrade-assistant',
'preupgrade-assistant-contents' or 'redhat-upgrade-tool'

However going to "Edit" mode, it is not possible to specify "is
any of" or "is not any of" condition.  I'm trying to add additional components to that list, and it is not possible.

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Hui Wang 2016-01-25 06:12:07 UTC

Verified this issue.
The result is PASS.
version 4.4.11048.1
Steps:
1. Edit rule:  'RHEL6 !Extras Keyword'
2. Add additional components in step2
3. See the details of the rule:

....
Component is not any of '389-ds-base', 'openvswitch', 'preupgrade-assistant', 'preupgrade-assistant-contents' or 'redhat-upgrade-tool'
..........

Adding the other component successfully.

Comment 2 Matt Tyson 🤬 2016-02-15 00:57:19 UTC

This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.