Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1810852[details]
anaconda log screenshot
Description of problem:
We (CentOS Infra team) are using the same kickstart to deploy CentOS Stream 8 on bare-metal nodes and when we tried to reinstall nodes (from CentOS 7 to CentOS Stream 8), it tracebacks, but same kickstart works fine with CentOS Linux 8 (that is going EOL soon)
Version-Release number of selected component (if applicable):
CentOS Stream 8
How reproducible:
create a kickstart that will configuring raid1 md devices and kick the install
Additional info:
Part of the common kickstart.j2 template rendered by ansible to deploy the node :
<snip>
# Partition clearing information
clearpart --all --initlabel
zerombr
# Disk partitioning information
# Adding first reqpart to automatically add /boot/efi or prepboot for aarch64, uefi, or IBM Power architectures
reqpart
# Using software raid 1
part raid.603 --fstype="mdmember" --ondisk=sdb --size=20000 --grow
part raid.469 --fstype="mdmember" --ondisk=sda --size=1024
part raid.597 --fstype="mdmember" --ondisk=sda --size=20000 --grow
part raid.475 --fstype="mdmember" --ondisk=sdb --size=1024
raid pv.609 --device=pv00 --fstype="lvmpv" --level=RAID1 raid.597 raid.603
raid /boot --device=boot --fstype="ext4" --level=RAID1 raid.469 raid.475
volgroup vg_kempty-n28 --pesize=4096 pv.609
</snip>
Adding screenshot from supermicro java kvm viewer for the log/traceback from anaconda, while it deploys fine with current CentOS Linux 8.4
The "mdadm: specifying chunk size is forbidden for this level" seems to be the pointer
I see that a new python-blivet correcting this was built : https://koji.mbox.centos.org/koji/buildinfo?buildID=18685
With changelog :
* Mon Aug 02 2021 Vojtech Trefny <vtrefny> - 3.4.0-4
- Do not set chunk size for RAID 1
Resolves: rhbz#1987170
I'll retry a redeploy with 8-stream but I can say that by looking at the QA stream logs, it passed this time, so should be "out".
I did a quick installation with the latest C8S (20210907) and I was able to finish the installation with RAID 1 (with python3-blivet-3.4.0-5.el8) so I think we can close this now. @farrotin I'm not sure how this works with CentOS Stream, can we just close this as duplicate of the RHEL bug (https://bugzilla.redhat.com/show_bug.cgi?id=1987170) or is there some special process for CentOS?
Created attachment 1810852 [details] anaconda log screenshot Description of problem: We (CentOS Infra team) are using the same kickstart to deploy CentOS Stream 8 on bare-metal nodes and when we tried to reinstall nodes (from CentOS 7 to CentOS Stream 8), it tracebacks, but same kickstart works fine with CentOS Linux 8 (that is going EOL soon) Version-Release number of selected component (if applicable): CentOS Stream 8 How reproducible: create a kickstart that will configuring raid1 md devices and kick the install Additional info: Part of the common kickstart.j2 template rendered by ansible to deploy the node : <snip> # Partition clearing information clearpart --all --initlabel zerombr # Disk partitioning information # Adding first reqpart to automatically add /boot/efi or prepboot for aarch64, uefi, or IBM Power architectures reqpart # Using software raid 1 part raid.603 --fstype="mdmember" --ondisk=sdb --size=20000 --grow part raid.469 --fstype="mdmember" --ondisk=sda --size=1024 part raid.597 --fstype="mdmember" --ondisk=sda --size=20000 --grow part raid.475 --fstype="mdmember" --ondisk=sdb --size=1024 raid pv.609 --device=pv00 --fstype="lvmpv" --level=RAID1 raid.597 raid.603 raid /boot --device=boot --fstype="ext4" --level=RAID1 raid.469 raid.475 volgroup vg_kempty-n28 --pesize=4096 pv.609 </snip> Adding screenshot from supermicro java kvm viewer for the log/traceback from anaconda, while it deploys fine with current CentOS Linux 8.4 The "mdadm: specifying chunk size is forbidden for this level" seems to be the pointer