Bug 1760704

Summary:	Enable RHTS for all Fedora versions
Product:	[Retired] Beaker	Reporter:	Pavel Raiskup <praiskup>
Component:	general	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	develop	CC:	bpeck, cbouchar, praiskup, rebarbos
Target Milestone:	---	Keywords:	EasyFix, Patch, Reopened, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1750646	Environment:
Last Closed:	2020-10-21 14:13:53 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:
Bug Depends On:	1750646
Bug Blocks:	1719226

Description Pavel Raiskup 2019-10-11 06:56:13 UTC

The repofiles have this:
baseurl=https://download.eng.bos.redhat.com/beakerrepos/client/Fedora$releasever/

But on F31 and F32 this doesn't work.

--- Additional comment from Martin Styk 🤦‍♂️ on 2019-10-11 08:31:23 CEST ---

(In reply to Pavel Raiskup from comment #1)
> I'm reopening this for F31 and F32.  Let me know if you rather want a new
> bug.

Please create a separate issue for F31 and F32. But I can tell right now, that we are blocked by our BREW builders for F31/32.

--- Additional comment from Pavel Raiskup on 2019-10-11 08:53:02 CEST ---

You can use internal copr for that, https://copr.devel.redhat.com/

--- Additional comment from Martin Styk 🤦‍♂️ on 2019-10-11 08:54:19 CEST ---

No, because RPM will be not signed.

Comment 1 Pavel Raiskup 2019-10-11 07:00:31 UTC

Would the signing workflow as is done in Fedora copr (i.e. gpg key generated
automatically by copr build system per copr project) work for you?

Comment 2 Martin Styk 2019-11-21 09:29:22 UTC

I was thinking about that for a while.

This is completely fine solution for our upstream packages.
But I will have to figure out how we are going to sync them and sign with current keys in RH.

Comment 3 Pavel Raiskup 2019-11-21 12:09:05 UTC

I don't propose building it in Fedora Copr, but we could implement the same
signing feature in Internal Copr.

> sign with current keys in RH.

We should be able to configure copr to use your key (if we added gpg signing
support), but you'd have to "trust" us enough to give us the keys.  At least
as long as you plan to let us do the automatic signatures.