Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1944900

Summary:	[RFE] When creating client RPMs from rhui-manager, fix releasever in repo paths instead of leaving it as a variable
Product:	Red Hat Update Infrastructure for Cloud Providers	Reporter:	Pablo Hess <phess>
Component:	RHUA	Assignee:	RHUI Bug List <rhui-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Radek Bíba <rbiba>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	3.1.7	CC:	mminar
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-26 13:36:35 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:

Description Pablo Hess 2021-03-30 21:35:56 UTC

When creating client RPMs with rhui-manager, the tool knows exactly what repositories are available to clients, so it should specify repository paths in full e.g.

  /pulp/contents/.../rhel/server/7/7Server/x86_64/os

instead of:

  /pulp/contents/.../rhel/server/7/$releasever/$basearch/os


This applies to any variables (releasever, basearch and whatnot) but the effects are more pronounced on the releasever variable. The impact this has on hosts is that any host that ends up setting a release version in /etc/yum/vars/releasever that conflicts with what the certs in the client RPM give access to will face errors when downloading from RHUI repositories.