What were you trying to do that didn't work?

NVMe-FC automation jobs are all failing for RHEL-10 CTC2. Upon further investigation, I noticed that after reboot, the nvme autoconnect is not being triggered - therefore no nvme namespaces are available unless I explicitly issue a discovery:

# echo 1 > /sys/devices/virtual/fc/fc_udev_device/nvme_discovery

Further analysis shows that the nvmefc-boot-connections.service is disabled:

# systemctl status nvmefc-boot-connections.service
○ nvmefc-boot-connections.service - Auto-connect to subsystems on FC-NVME devices found during boot
     Loaded: loaded (/usr/lib/systemd/system/nvmefc-boot-connections.service; disabled; preset: disabled)
     Active: inactive (dead)

This was not an issue with RHEL-10 CTC1 with nvme-cli-2.10.2-1.el10. Below is a job where the problem is observed:

https://beaker.engineering.redhat.com/jobs/10542786

Not sure if related, but the /usr/lib/systemd/system-preset/90-default.preset file does not have any entries for nvme  - the same file in RHEL-9.6 includes the following:

# cat /usr/lib/systemd/system-preset/90-default.preset |grep nvme
nvme auto connect
enable nvmefc-boot-connections.service

What is the impact of this issue to you?

NVMe-FC autoconnect stopped working impacting all the nvme-fc automation

Please provide the package NVR for which the bug is seen:

nvme-cli-2.11-3.el10.x86_64

kernel-6.12.0-38.el10

How reproducible is this bug?: Often