Bug 1034230 - cannot start targetd, it requires missing targetcli.service
Summary: cannot start targetd, it requires missing targetcli.service
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: targetd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Andy Grover
QA Contact: Bruno Goncalves
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-25 13:13 UTC by Petr Sklenar
Modified: 2021-09-06 12:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:54:24 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Petr Sklenar 2013-11-25 13:13:44 UTC
Description of problem:
I cannot start targetd with default configuration
there is missing file targetcli.service in the targetcli-2.1.fb31-1.el7.noarch

Version-Release number of selected component (if applicable):
rpm -q targetd targetcli
targetd-0.6.1-1.el7.noarch
targetcli-2.1.fb31-1.el7.noarch

How reproducible:
always

Steps to Reproduce:
1. systemctl start targetd
Failed to issue method call: Unit targetcli.service failed to load: No such file or directory.

2. grep Requires /usr/lib/systemd/system/targetd.service
Requires=targetcli.service

3. rpm -ql targetcli | grep systemd


Actual results:
but there isn't any targetcli service in the targetcli packages

Expected results:
I can start targetd

Additional info:
there is /usr/lib/systemd/system/targetcli.service on my fedora19:
rpm -qf /usr/lib/systemd/system/targetcli.service
targetcli-2.1.fb30-1.fc19.noarch

Comment 5 Bruno Goncalves 2014-02-17 16:17:59 UTC
Verified with:
targetcli-2.1.fb31-2.el7.noarch
targetd-0.7.1-1.el7.noarch

# grep Requires /usr/lib/systemd/system/targetd.service
Requires=target.service

# systemctl start targetd


# systemctl status targetd
targetd.service - targetd storage array API daemon
   Loaded: loaded (/usr/lib/systemd/system/targetd.service; disabled)
   Active: failed (Result: exit-code) since Mon 2014-02-17 11:10:10 EST; 12s ago
  Process: 26834 ExecStart=/usr/bin/targetd (code=exited, status=255)
 Main PID: 26834 (code=exited, status=255)

Feb 17 11:10:10 storageqe-01.rhts.eng.bos.redhat.com systemd[1]: Starting targetd storage array API daemon...
Feb 17 11:10:10 storageqe-01.rhts.eng.bos.redhat.com systemd[1]: Started targetd storage array API daemon.
Feb 17 11:10:10 storageqe-01.rhts.eng.bos.redhat.com targetd[26834]: CRITICAL:root:password not set in /etc/target/targetd.yaml
Feb 17 11:10:10 storageqe-01.rhts.eng.bos.redhat.com systemd[1]: targetd.service: main process exited, code=exited, status=255/n/a
Feb 17 11:10:10 storageqe-01.rhts.eng.bos.redhat.com systemd[1]: Unit targetd.service entered failed state.

NOTE: service is not running because I used default settings and root password is not set.



# systemctl status target
target.service - Restore LIO kernel target configuration
   Loaded: loaded (/usr/lib/systemd/system/target.service; disabled)
   Active: active (exited) since Mon 2014-02-17 11:10:10 EST; 15s ago
  Process: 26770 ExecStop=/usr/bin/targetctl clear (code=exited, status=0/SUCCESS)
  Process: 26828 ExecStart=/usr/bin/targetctl restore (code=exited, status=0/SUCCESS)
 Main PID: 26828 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/target.service

Comment 6 Ludek Smid 2014-06-13 11:54:24 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.