To work around a potential linking issue between
nvme-cli ad libnvme that prevents nvme-cli from
correctly generating a hostnqn, causing
nvme_fabrics: found same hostid
edb4e426-766f-44c6-b127-
da2a5b7446ef but different hostnqn hostnqn
messages in dmesg and the inability to setup nvme
loop devices
Fixes: https://tracker.ceph.com/issues/67684
Signed-off-by: Adam King <adking@redhat.com>
(cherry picked from commit
4e5f269c01dd94741fbddaa7f76ebe4ac155e650)
tasks:
- pexec:
all:
+ # in order to work around a possible nvme-cli <-> libnvme linking issue
+ # See https://tracker.ceph.com/issues/67684
+ - sudo dnf remove nvme-cli -y
- sudo dnf install nvmetcli nvme-cli -y
tasks:
- pexec:
all:
+ # in order to work around a possible nvme-cli <-> libnvme linking issue
+ # See https://tracker.ceph.com/issues/67684
+ - sudo dnf remove nvme-cli -y
- sudo dnf install runc nvmetcli nvme-cli -y
- sudo sed -i 's/^#runtime = "crun"/runtime = "runc"/g' /usr/share/containers/containers.conf
- sudo sed -i 's/runtime = "crun"/#runtime = "crun"/g' /usr/share/containers/containers.conf