Bug 1849941

Summary:	foreman-maintain enables rhel-7-server-satellite-tools-6.8-beta-rpms repo instead of rhel-7-server-satellite-tools-6-beta-rpms for beta scenario.
Product:	Red Hat Satellite	Reporter:	Jameer Pathan <jpathan>
Component:	Satellite Maintain	Assignee:	Suraj Patil <supatil>
Status:	CLOSED ERRATA	QA Contact:	Jameer Pathan <jpathan>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8.0	CC:	apatel, aupadhye, ehelms, gtalreja, kgaikwad, supatil
Target Milestone:	6.8.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rubygem-foreman_maintain-0.6.8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-27 12:38:24 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 Jameer Pathan 2020-06-23 09:02:36 UTC

Description of problem:
foreman-maintain enables rhel-7-server-satellite-tools-6.8-beta-rpms repo instead of rhel-7-server-satellite-tools-6-beta-rpms for beta scenario.

Version-Release number of selected component (if applicable):
- Satellite 6.8.0 snap 5
- rubygem-foreman_maintain-0.6.5-1

How reproducible:
- Always

Steps to Reproduce:
1.export FOREMAN_MAINTAIN_USE_BETA=1
2.foreman-maintain advanced procedure run repositories-setup --version 6.8

Actual results:
Error: 'rhel-7-server-satellite-tools-6.8-beta-rpms' does not match a valid repository ID. Use "subscription-manager repos --list" to see valid repositories.

Expected results:
- All required beta repositories gets enabled. i.e rhel-server-7-satellite-6-beta-rpms, rhel-7-server-ansible-2.8-rpms, rhel-7-server-satellite-maintenance-6-beta-rpm, rhel-server-rhscl-7-rpms, rhel-7-server-rpms, rhel-7-server-satellite-tools-6-beta-rpms.

Additional info:

Comment 1 Suraj Patil 2020-06-24 10:10:31 UTC

Created redmine issue https://projects.theforeman.org/issues/30204 from this bug

Comment 2 Bryan Kearney 2020-07-04 20:04:06 UTC

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/30204 has been resolved.

Comment 3 Jameer Pathan 2020-07-20 10:23:49 UTC

Verified:

Verified with:
- Satellite 6.8.0 snap 9
- rubygem-foreman_maintain-0.6.8-1.el7sat.noarch

Test Steps:
1.export FOREMAN_MAINTAIN_USE_BETA=1
2.foreman-maintain advanced procedure run repositories-setup --version 6.8

Observation:
- All required beta repositories were enabled. i.e rhel-server-7-satellite-6-beta-rpms, rhel-7-server-ansible-2.8-rpms, rhel-7-server-satellite-maintenance-6-beta-rpm, rhel-server-rhscl-7-rpms, rhel-7-server-rpms, rhel-7-server-satellite-tools-6-beta-rpms.

Comment 6 errata-xmlrpc 2020-10-27 12:38:24 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 (Satellite 6.8 Satellite Maintenance Release), 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-2020:4365