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 1934175 - leapp has no documentation for mdadm systems
Summary: leapp has no documentation for mdadm systems
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.9
Hardware: All
OS: Linux
medium
urgent
Target Milestone: rc
: ---
Assignee: Leapp team
QA Contact: Alois Mahdal
URL:
Whiteboard:
Depends On:
Blocks: 1818077 1818088
TreeView+ depends on / blocked
 
Reported: 2021-03-02 16:27 UTC by jcastran
Modified: 2024-10-01 17:35 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-05 10:51:50 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1957192 1 medium CLOSED RFE: handle in-place upgrades with software RAIDs (mdadm) 2024-10-01 18:06:25 UTC

Description jcastran 2021-03-02 16:27:00 UTC 
Description of problem:
There is nothing detailing if mdadm is allowed, or if there are additional options required. 

upgrade initramfs does not include mdadm


It's done in:
/usr/share/leapp-repository/repositories/system_upgrade/el7toel8/actors/initramdiskgenerator/files/generate-initram.sh line 43.


Version-Release number of selected component (if applicable):
leapp-0.12.0-1.el7_9.noarch

How reproducible:
leapp upgrade

Steps to Reproduce:
1. leapp upgrade


Actual results:
# lsinitrd /boot/initramfs-upgrade.x86_64.img | grep mdadm
#

# grep nomdadm /var/log/leapp/leapp-upgrade.log
Arguments: -v -v -v -v --force --conf '/dev/null' --confdir '/var/empty' --install 'systemd-nspawn' --add 'sys-upgrade-redhat' --add 'sys-upgrade' --nomdadmconf --nolvmconf --no-hostonly --kver '4.18.0-193.28.1.el8_2.x86_64' --kernel-image 'vmlinuz-upgrade.x86_64'


Expected results:
mdadm should be loaded when required for upgrades or this should be documented. 

Additional info:

Is there a requirement to use LEAPP_DRACUT_MDADMCONF=1 on systems with mdadm drives?

  # export LEAPP_DRACUT_MDADMCONF=1
  # leapp upgrade

Is this expected to automatically detect and include mdadm when pertinent?

    DRACUT_MDADMCONF_ARG="--nomdadmconf"
    if [[ ! -z "$LEAPP_DRACUT_MDADMCONF" ]]; then
        # include local /etc/mdadm.conf
        DRACUT_MDADMCONF_ARG="--mdadmconf"
    fi
Comment 2 Petr Stodulka 2021-03-02 16:55:38 UTC 
Hi John.
let me to split it into the two parts:
1) No, documentation is not missing from that POV.
Setting the LEAPP_DRACUT_MDADMCONF envar will not have any effect as the script is executed inside container and this particular envar is not passed with it (if you run leapp with --debug, you can see it [snippet below]). You can think about that piece of code like it's not there for now.

2) We can call it bug or RFE to make upgrades with RAIDs working.
Looking into it a little bit more, the code will not be even working properly,
as the /etc/mdadm.conf is not present in the container where the script is executed
right now. If I understand well, two things has to happened:
- RAID needs to be detected
- if detected, the information has to be passed to the script and the config file
  has to be present (copied) into the container.
Can you confirm the configuration file is compatible between RHEL 7 & 8?
I am not SME in this area, so asking just to know better the scope of the solution.

Prerequisite for the patch is merge of the following feature PR in upstream:
  https://github.com/oamg/leapp-repository/pull/517
Comment 3 Petr Stodulka 2021-03-02 17:11:32 UTC 
Correction: I realized the point 1) is wrong. The LEAPP_DRACUT_MDADMCONF is nowadays populated into the container so script is affected by it. However the configuration file is not present, so it seems still buggy to me.
Comment 5 Petr Stodulka 2021-05-05 10:51:50 UTC 
We are going to document the new limitation in the upgrade article. The change will be published with/after the RHEL 8.4 GA. Closing the bug. In case the support for software RAIDs is wanted, follow the bug 1957192. We suggest to move customer cases that requires the new feature into that BZ to help with prioritisation.
Note You need to log in before you can comment on or make changes to this bug.