Description of problem: /etc/target/saveconfig.json is introduced as a directory instead of a file in the container image. As a result, target service doesn't come up. sh-4.2# systemctl status target -l ● target.service - Restore LIO kernel target configuration Loaded: loaded (/usr/lib/systemd/system/target.service; disabled; vendor preset: disabled) Active: inactive (dead) since Thu 2017-08-24 12:37:29 UTC; 13min ago Process: 2424 ExecStop=/usr/bin/targetctl clear (code=exited, status=0/SUCCESS) Process: 2405 ExecStart=/usr/bin/targetctl restore (code=exited, status=0/SUCCESS) Main PID: 2405 (code=exited, status=0/SUCCESS) Aug 24 12:37:25 dhcp46-203.lab.eng.blr.redhat.com systemd[1]: Starting Restore LIO kernel target configuration... Aug 24 12:37:25 dhcp46-203.lab.eng.blr.redhat.com target[2405]: No saved config file at /etc/target/saveconfig.json, ok, exiting Aug 24 12:37:25 dhcp46-203.lab.eng.blr.redhat.com systemd[1]: Started Restore LIO kernel target configuration. Aug 24 12:37:29 dhcp46-203.lab.eng.blr.redhat.com systemd[1]: Stopping Restore LIO kernel target configuration... Aug 24 12:37:29 dhcp46-203.lab.eng.blr.redhat.com systemd[1]: Stopped Restore LIO kernel target configuration. Version-Release number of selected component (if applicable): cns-deploy-5.0.0-21.el7rhgs.x86_64 (with the How reproducible: Always Steps to Reproduce: 1. deploy cns and check for target service and gluster-blockd service
This was an issue in bind mount of /etc/target which is corrected now in the template and next cns-build will have the fix.
Verified the fix in build - cns-deploy-5.0.0-23.el7rhgs.x86_64 gluster-block-target service starts without any issues and the configuration file is stored in /etc/target/saveconfig.json sh-4.2# ls -l /etc/target/saveconfig.json -rw-------. 1 root root 24696 Aug 29 06:17 /etc/target/saveconfig.json snippet of gluster-template: volumeMounts: - mountPath: /etc/target name: glusterfs-gblock Moving the bug to verified.
Changed the doc text a little bit. Looks good to me.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2017:2877