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 2017107 - Backport IMSM Software Raid code
Summary: Backport IMSM Software Raid code
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: rear
Version: 7.9
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Pavel Cahyna
QA Contact: CS System Management SST QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-25 15:39 UTC by Renaud Métrich
Modified: 2023-09-21 23:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-21 23:39:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
XML to create a QEMU/KVM (7.80 KB, text/plain)
2021-10-25 15:41 UTC, Renaud Métrich 		no flags Details
Kickstart to build a fake IMSM VM (needs some hacks, see inside) (2.48 KB, text/plain)
2021-10-25 15:43 UTC, Renaud Métrich 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github rear rear pull 2702 0 None open Software RAID: IMSM support 2021-10-25 15:45:39 UTC
Red Hat Issue Tracker   RHEL-6958 0 None Migrated None 2023-09-21 23:39:32 UTC
Red Hat Issue Tracker RHELPLAN-100637 0 None None None 2021-10-25 15:39:33 UTC

Description Renaud Métrich 2021-10-25 15:39:02 UTC 
Description of problem:

Last week I struggled with a customer trying to restore IMSM Software Raid. It appears that the current code doesn't work at all.
I've come up with PR https://github.com/rear/rear/pull/2702 which should be easily backportable to RHEL7.

I think it's a must-have because it's very complicated to restore manually in case software raid is present.

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

2.4 and 2.6

How reproducible:

Always

Steps to Reproduce:
1. Install a QEMU/KVM with 2 SCSI Disks having a SCSI ID

  XML and kickstart attached for reference.

2. Create ReaR ISO

3. Clone the VM and try to restore it

Actual results:

Various failures in the disk restore phase
Comment 3 Renaud Métrich 2021-10-25 15:41:32 UTC 
Created attachment 1836924 [details]
XML to create a QEMU/KVM
Comment 4 Renaud Métrich 2021-10-25 15:43:08 UTC 
Created attachment 1836925 [details]
Kickstart to build a fake IMSM VM (needs some hacks, see inside)
Comment 5 Pavel Cahyna 2021-10-25 16:01:04 UTC 
duplicate of bz1995861 ?
Comment 6 Renaud Métrich 2021-10-26 07:34:25 UTC 
Not really a dup of this one, which seems different.
Here rear was just failing to execute mdadm commands due to bad parameters saved in disklayout.conf
Comment 8 Pavel Cahyna 2021-11-16 15:45:34 UTC 
So, there is a problem: we need to create arrays with the same UUIDs as on the original system, but mdadm does not allow setting UUID on IMSM arrays, it ignores the --uuid option and always creates a random UUID. https://github.com/rear/rear/pull/2702#issuecomment-970395567
Comment 11 RHEL Program Management 2023-09-21 23:35:40 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-21 23:39:38 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.
Note You need to log in before you can comment on or make changes to this bug.