[PATCH] nvmetcli: set up the target only after the network is configured

Maurizio Lombardi mlombard at redhat.com
Tue Feb 28 08:36:15 PST 2023


network.target only indicates that the network stack is up, but it
doesn't mean that the network devices have been configured.

Replace it with network-online.target, this fixes the following
error when systemd restores the target configuration during boot:

[   19.613251] nvmet_tcp: failed to bind port socket -99
[FAILED] Failed to start Restore NVMe kernel target configuration.

Signed-off-by: Maurizio Lombardi <mlombard at redhat.com>
---
 nvmet.service | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/nvmet.service b/nvmet.service
index 5c7991e..6f97a91 100644
--- a/nvmet.service
+++ b/nvmet.service
@@ -1,7 +1,8 @@
 [Unit]
 Description=Restore NVMe kernel target configuration
 Requires=sys-kernel-config.mount
-After=sys-kernel-config.mount network.target local-fs.target
+After=sys-kernel-config.mount network-online.target local-fs.target
+Wants=network-online.target
 
 [Service]
 Type=oneshot
-- 
2.31.1




More information about the Linux-nvme mailing list