boot startup: some backing-store luns not created

[Rich Hornay]

System: 18.04.2, tgt ver:1.0.72

With many targets listed in targets.conf (I have 10), tgtd intermittently does not add the backing-store lun (LUN 1) to the target. Seems to be random as to which target.

Even with debug logging turned on, tgtd gives no indication of failure or why it skipped a backing-store.

Once startup is complete, a restart of tgtd will setup targets correctly.

WORKAROUND:
Pushing tgtd startup later in the cycle seems to create targets as expected. Something must interfere with tgtd during the LUN creation.

tgt.service:
[Unit]
#After=network.target
After=network-online.target

Note: This seems to be new behavior manifesting on systemd systems as opposed to sysv systems.