This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2222859 - repomap.json missing support for resilient storage channel
Summary: repomap.json missing support for resilient storage channel
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: leapp-repository
Version: 8.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: upgrades-and-conversions
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-14 07:45 UTC by Fabio Massimo Di Nitto
Modified: 2024-01-11 04:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-12 14:47:24 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OAMG-9429 0 None None None 2023-07-14 07:45:57 UTC
Red Hat Issue Tracker   RHEL-3363 0 None Migrated None 2023-09-12 14:47:34 UTC
Red Hat Issue Tracker RHELPLAN-162347 0 None None None 2023-07-14 07:45:50 UTC
Red Hat Knowledge Base (Article) 7012677 0 None None None 2023-07-14 07:45:06 UTC

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