Bug 1656448

Summary:	gnome-boxes should rather promote RHEL and Fedora
Product:	Red Hat Enterprise Linux 7	Reporter:	Tomas Pelka <tpelka>
Component:	gnome-boxes	Assignee:	Felipe Borges <feborges>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.7	CC:	cfergeau, desktop-qa-list, feborges, fidencio, jeischma, jkoten, mboisver, vbudikov
Target Milestone:	rc
Target Release:	7.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gnome-boxes-3.28.5-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1656446	Environment:
Last Closed:	2019-08-06 12:37:49 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:
Embargoed:
Bug Depends On:	1656446
Bug Blocks:

Description Tomas Pelka 2018-12-05 14:33:28 UTC

+++ This bug was initially created as a clone of Bug #1656446 +++

Description of problem:
we should rather promote RHEL and Fedora over our competitors 

Version-Release number of selected component (if applicable):
libosinfo-1.2.0-4.el8.x86_64
gnome-boxes-3.28.5-2.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. start gnome-boxes
2. hit new
3.

Actual results:
Ubintu and Suse are on the top of the list

Expected results:
RHEL and Fedora should be there instead

Additional info:
Felipe mentione that there is a way how to do it in some sort of xml, backport from 3.30 would be needed if I understood correctly.

--- Additional comment from Tomas Pelka on 2018-12-05 09:31:24 EST ---

And we might want to backport to 7.7 too

Comment 4 errata-xmlrpc 2019-08-06 12:37:49 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2044