Bug 2222859

Summary:	repomap.json missing support for resilient storage channel
Product:	Red Hat Enterprise Linux 8	Reporter:	Fabio Massimo Di Nitto <fdinitto>
Component:	leapp-repository	Assignee:	Petr Stodulka <pstodulk>
Status:	CLOSED MIGRATED	QA Contact:	upgrades-and-conversions
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.8	CC:	cfeist, djansa, mkluson, pholica
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-12 14:47: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 Fabio Massimo Di Nitto 2023-07-14 07:45:06 UTC

Description of problem:

run leapp preupgrade with resilient storage channel is enabled and packages are installed will lead to:

Risk Factor: low
Title: Some enabled RPM repositories are unknown to Leapp
Summary: The following repositories with Red Hat-signed packages are unknown to Leapp:
- rhel-8-for-x86_64-resilientstorage-rpms
And the following packages installed from those repositories may not be upgraded:
- dlm
- [SNIP]
Remediation: [hint] You can file a request to add this repository to the scope of in-place upgrades by filing a support ticket
Key: 8e89e20c645cea600b240156071d81c64daab7ad

Version-Release number of selected component (if applicable):

0.18.0-1.el8_8.2

How reproducible:

always

Steps to Reproduce:
1. on any rhel8.8 machine
2. subscription-manager repos --enable rhel-8-for-x86_64-resilientstorage-rpms
2. yum install dlm
3. leapp preupgrade

Actual results:

as above, we get an error and the equivalent channel for rhel-9 is not enabled.

Expected results:

rhel-9-for-x86_64-resilientstorage-rpms enabled and used for the upgrade.

Additional info:

I have temporary worked around the problem by editing /etc/leapp/files/repomap.json and once resiliatstorage is enabled, it works like a champ :)

Comment 1 Petr Stodulka 2023-07-14 09:50:36 UTC

Hi, thank you for the report. It will be discussed for teams working on resilient storage.
There is no need to update repomap.json for the workaround, it's possible to just apply the use of the repository manually when running leapp, in this case e.g.:
   # leapp upgrade --enablerepo rhel-9-for-x86_64-resilientstorage-rpms

Comment 3 Fabio Massimo Di Nitto 2023-07-14 09:59:25 UTC

(In reply to Petr Stodulka from comment #1)
> Hi, thank you for the report. It will be discussed for teams working on
> resilient storage.
> There is no need to update repomap.json for the workaround, it's possible to
> just apply the use of the repository manually when running leapp, in this
> case e.g.:
>    # leapp upgrade --enablerepo rhel-9-for-x86_64-resilientstorage-rpms

I see the difference with the command I used. I set --enablerepo with the rhel-8-* version and not 9.

Tho it would be still nice to see it incorporated and less manual mingling from the end user.

Comment 11 RHEL Program Management 2023-09-12 14:46:14 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 12 RHEL Program Management 2023-09-12 14:47:24 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 13 Red Hat Bugzilla 2024-01-11 04:25:16 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days