Bug 1300366 - "any of" / "not any of" not appearing in BRE component picker
Summary: "any of" / "not any of" not appearing in BRE component picker
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Internal Tools
Version: 4.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 4.4
Assignee: Matt Tyson 🤬
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-20 15:04 UTC by Tom Lavigne
Modified: 2018-12-09 06:29 UTC (History)
7 users (show)

Fixed In Version: 4.4.11048.2
Clone Of:
Environment:
Last Closed: 2016-02-15 00:57:19 UTC
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.