Bug 2017107

Summary: Backport IMSM Software Raid code
Product: Red Hat Enterprise Linux 7 Reporter: Renaud Métrich <rmetrich>
Component: rearAssignee: Pavel Cahyna <pcahyna>
Status: CLOSED MIGRATED QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: high Docs Contact:
Priority: high    
Version: 7.9CC: fkrska, ovasik, pcahyna
Target Milestone: rcKeywords: MigratedToJIRA
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-21 23:39:38 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:
Attachments:
Description Flags
XML to create a QEMU/KVM
none
Kickstart to build a fake IMSM VM (needs some hacks, see inside) none

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.