Bug 743077

Summary:	Blacklist "This release or newer"
Product:	[Retired] Beaker	Reporter:	Sean Waite <swaite>
Component:	web UI	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	low
Version:	0.7	CC:	bpeck, jbulger, jnicolet, mastyk, mcsontos, stl, tools-bugs
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	Misc
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-02 11:54:22 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sean Waite 2011-10-03 19:03:52 UTC

We've had a use case on occasion for blacklisting a system's ability to install a particular release, or newer, on the excluded families tab. For instance - we have an older prototype that is still useful for testing, but the hardware isn't supported in kernels post 2.6.32-179.el6, causing it to fail on RHEL6.2 and greater. There are still cases where we'd test older releases (and, it seems to still be supported in RHEL5), but we'll have to blacklist every release on the RHEL6 tree from here on out, by hand, per system.

Comment 1 Bill Peck 2011-10-03 19:07:02 UTC

because version releases are not numerical and we have rhel and fedora which have overlapping numbers..  Can we instead support flipping the exclude to a include list?  I think the default exclude is the most common but we could support turning it into an include list as well.  You would have to pick per system if you want exclude or include, you wouldn't be able to pick from both.

Comment 2 Sean Waite 2011-10-03 19:23:12 UTC

(In reply to comment #1)
> because version releases are not numerical and we have rhel and fedora which
> have overlapping numbers..  Can we instead support flipping the exclude to a
> include list?  I think the default exclude is the most common but we could
> support turning it into an include list as well.  You would have to pick per
> system if you want exclude or include, you wouldn't be able to pick from both.

Per our little chat:
-The radio button toggles make sense, given the complexity of a per-major-release include/exclude
-The ability for beaker to "do the right thing" and properly convert an include list to an exclude list (and vice versa) as you switch between excludes and includes would go a long way towards making this even better.

Comment 5 Martin Styk 2020-06-02 11:54:22 UTC

Hello,

thank you for opening issue in Beaker project.
This issue was marked with component "web ui".
As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX.
New UI will be reimplemented within new versions of Beaker.

If you have any questions feel free to reach out to me.

Best regards,
Martin <martin.styk>