Closed noelmcloughlin closed 4 years ago
Identical on Archlinux. Service starts but pillar data is incomplete.
* target.service - Restore LIO kernel target configuration
Loaded: loaded (/usr/lib/systemd/system/target.service; enabled; vendor preset: disabled)
Active: active (exited) since Sat 2019-09-21 06:35:37 AEST; 233ms ago
Main PID: 5330 (code=exited, status=0/SUCCESS)
Tasks: 0
Memory: 0B
CGroup: /system.slice/target.service
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: 'name' not defined in fabricmodule 1, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: 'wwn' not defined in target 0, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: Could not find matching StorageObject for LUN 0, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: Could not find matching StorageObject for LUN 1, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: Could not find matching StorageObject for LUN 2, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: Could not find matching StorageObject for LUN 3, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: Could not find matching StorageObject for LUN 4, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: 'port' field missing from a portal in TPG 2, skipped
Sep 21 06:35:37 archlinux.vagrant.vm target[5330]: 'node_wwn' missing in node_acl, skipped
Sep 21 06:35:37 archlinux.vagrant.vm systemd[1]: Started Restore LIO kernel target configuration.
This is actually okay. The configuration is valid and sufficient for travis.
The LIO example in the
pillar.example
has a few discrepencies.