Bug 1944900 - [RFE] When creating client RPMs from rhui-manager, fix releasever in repo paths instead of leaving it as a variable
Summary: [RFE] When creating client RPMs from rhui-manager, fix releasever in repo pat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: RHUA
Version: 3.1.7
Hardware: All
OS: Linux
unspecified
low
Target Milestone: ---
: ---
Assignee: RHUI Bug List
QA Contact: Radek Bíba
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-30 21:35 UTC by Pablo Hess
Modified: 2021-07-26 13:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-26 13:36:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

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