Page MenuHomeVyOS Platform
Create Task
Maniphest T5208

Failed to start nvmf-autoconnect.service during the boot
Closed, ResolvedPublicBUG
Actions

Description

The log after reboot

[  OK  ] Started vyos-router.service - VyOS Router.
         Starting systemd-user-sess…vice - Permit User Sessions...
[FAILED] Failed to start nvmf-autoc…systems automatically during boot.
See 'systemctl status nvmf-autoconnect.service' for details.

Status modprobe[1025]: modprobe: FATAL: Module nvme-fabrics not found in directory /lib/modules/6.1.27-amd64-vyos

vyos@r14:~$ sudo systemctl status nvmf-autoconnect.service
× nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot
     Loaded: loaded (/lib/systemd/system/nvmf-autoconnect.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Mon 2023-05-08 12:23:45 EEST; 1min 18s ago
        CPU: 3ms

May 08 12:23:45 r14 systemd[1]: Starting nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot...
May 08 12:23:45 r14 modprobe[1025]: modprobe: FATAL: Module nvme-fabrics not found in directory /lib/modules/6.1.27-amd64-vyos
May 08 12:23:45 r14 systemd[1]: nvmf-autoconnect.service: Control process exited, code=exited, status=1/FAILURE
May 08 12:23:45 r14 systemd[1]: nvmf-autoconnect.service: Failed with result 'exit-code'.
May 08 12:23:45 r14 systemd[1]: Failed to start nvmf-autoconnect.service - Connect NVMe-oF subsystems automatically during boot.
vyos@r14:~$

Details

Difficulty level
Easy (less than an hour)
Version
VyOS 1.4-rolling-202305080742
Why the issue appeared?
Issues in third-party code
Is it a breaking change?
Perfectly compatible
Issue type
Cosmetic issue (typos etc.)

Event Timeline

Viacheslav created this task.May 8 2023, 9:29 AM
pasik added a subscriber: pasik.May 8 2023, 10:18 AM
c-po closed this task as Resolved.May 17 2023, 1:55 PM
c-po claimed this task.
c-po triaged this task as Low priority.
c-po changed Difficulty level from Unknown (require assessment) to Easy (less than an hour).
c-po changed Why the issue appeared? from Will be filled on close to Issues in third-party code.
c-po changed Is it a breaking change? from Unspecified (possibly destroys the router) to Perfectly compatible.
c-po changed Issue type from Bug (incorrect behavior) to Cosmetic issue (typos etc.).