Package: python3-rtslib-fb Version: 2.1.66-2 Severity: important Dear Maintainer,
I've also posted about this at debian-openst...@lists.debian.org because I'm not 100% sure it is a bug, but after a day my message is not in the list archives so I'm not sure it was actually received (there are no messages in the archive for 2019 at all). The issue I'm experiencing is that after a reboot, all targetcli configuration is gone despite there being a file with the saved desired state under /etc/rtslib-fb-target/saveconfig.json Investigating further with dpkg, targetcli-fb and python3-rtslib-fb seem not to provide any kind of service unit files or init scripts. After issuing targetctl restore manually, the desired state is restored. Am I missing something here? Is this intentional? The man page for targetcli explicitly states that distributions should ship service files to restore configuration after a reboot. I've also noticed that this package does ship with rtslib-fb-targetctl.service on debian stretch. So I'm inclined to believe this is a bug, after all. Versions (running debian buster/unstable): # dpkg -l | egrep 'rtslib|target' ii python-rtslib-fb-doc 2.1.66-2 ii python3-rtslib-fb 2.1.66-2 ii targetcli-fb 2.1.48-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/32 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-rtslib-fb depends on: ii python3 3.7.2-1 ii python3-pyudev 0.21.0-1 ii python3-six 1.12.0-1 python3-rtslib-fb recommends no packages. Versions of packages python3-rtslib-fb suggests: ii python-rtslib-fb-doc 2.1.66-2 -- no debconf information
