Bug 981906 - iscsi service will not start with force option
iscsi service will not start with force option
Status: CLOSED CURRENTRELEASE
Product: oVirt
Classification: Community
Component: vdsm (Show other bugs)
3.2
Unspecified Linux
unspecified Severity high
: ---
: 3.3.4
Assigned To: Douglas Schilling Landgraf
Haim
storage
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-06 17:10 EDT by Theron Conrey
Modified: 2016-02-10 15:19 EST (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-07-28 10:37:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 16527 None None None Never

  None (edit)
Description Theron Conrey 2013-07-06 17:10:26 EDT
Description of problem:

iscsi force-start does not work with systemd.  The envionment is Fedora 18.  


Version-Release number of selected component (if applicable):


How reproducible:

100%


Steps to Reproduce:
1. Fedora 18 minimal install.  
2. Add oVirt repo.  
3. Add to oVirt Cluster
4. oVirt component installation completes
5. system reboots
6. vdsm does not start.

Actual results:


Expected results:


Additional info:

removing the force option /lib/systemd/systemd-vdsmd allows the service to start.
Comment 1 Theron Conrey 2013-07-06 17:15:22 EDT
Correction:  Fedora 19 install.

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