Closed khassel closed 1 year ago
Hi @khassel,
Unfortunately not even Centos 7.9 has picked up the "-C" switch for multipath. There is a workaround, that may work for you, where you can install device-mapper-multipath 0.8.4 from the EPEL-8 repository. Below are instructions where we were able to make this work in our lab environment. These installation steps may vary depending on your current Centos configuration. We strongly suggest that you test and verify this change before rolling out in a production environment.
1. Install the following packages:
> sudo yum install -y lsscsi iscsi-initiator-utils sg3_utils
2. Create file /etc/yum.repos.d/test.repo with this content:
> [EPEL-8]
> baseurl = http://mirror.centos.org/centos/8-stream/BaseOS/x86_64/os
> enabled = 1
> gpgcheck = 0
> name = EPEL8 RPMs
> skip_if_unavailable = 1
3. Install device-mapper-multipath 0.8.4
> sudo yum install device-mapper-multipath.x86_64
4. Verify that iscsi-initiator-utils version is 6.2.0.874-2.el7 or later:
> rpm -q iscsi-initiator-utils
5. Set scanning to manual:
> sudo sed -i 's/^\(node.session.scan\).*/\1 = manual/' /etc/iscsi/iscsid.conf
6. Enable multi pathing:
> sudo mpathconf --enable --with_multipathd y --find_multipaths n
7. Ensure that iscsid and multipathd are running:
> sudo systemctl enable --now iscsid multipathd
8. Enable and start iscsi:
> sudo systemctl enable --now iscsi
Hi @khassel,
It was pointed out to me that the /etc/yum.repos.d/test.repo needs to be removed after installing device-mapper-multipath 0.8.4. This is so that the EPEL 8 repo doesn't conflict with future package management installs and updates.
Thank you for your replies @gnarl
There is a workaround, that may work for you ... We strongly suggest that you test and verify this change before rolling out in a production environment.
We decided to stay on the last v22 trident version until we have another node os running.
May you should highlight in the docs that running trident v23 with optap-san on centos7 nodes is not possible without the above workaround.
with Centos7, I also had to upgrade RPM before moving to the DMM update
the following did the trick (test on the NetApp Lab on Demand for Trident & Kubernetes)
rpm -q rpm
rpm-4.11.3-32.el7.x86_64
rpm -Uvh http://mirror.centos.org/centos/7/updates/x86_64/Packages/rpm-4.11.3-46.el7_9.x86_64.rpm \
https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/rpm-libs-4.11.3-46.el7_9.x86_64.rpm \
https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/rpm-python-4.11.3-46.el7_9.x86_64.rpm \
https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/rpm-build-4.11.3-46.el7_9.x86_64.rpm \
https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/rpm-build-libs-4.11.3-46.el7_9.x86_64.rpm \
https://rpmfind.net/linux/centos/7.9.2009/updates/x86_64/Packages/rpm-sign-4.11.3-46.el7_9.x86_64.rpm
rpm -q rpm
rpm-4.11.3-46.el7_9.x86_64
Describe the bug
With
v23.01.0
new code was introduced here which callsmultipath -C /dev-dm...
.We are using centos7 Nodes with
multipath-tools v0.4.9 (05/33, 2016)
, this version has no-C
switch.This leads to problems when mounting an iscsi volume, here some logs of the
trident
pod:We had to roll back to
v22
.Environment
v23.01.0
v20.10.21
v1.23.8
v2.7.1
To Reproduce see description
Expected behavior trident
v23
should work with centos7 Nodes