Bug 1664662

Summary:	systemd unit starts vdo too early when using iscsi backing device
Product:	Red Hat Enterprise Linux 7	Reporter:	michal novacek <mnovacek>
Component:	vdo	Assignee:	corwin <corwin>
Status:	CLOSED DUPLICATE	QA Contact:	Filip Suba <fsuba>
Severity:	unspecified	Docs Contact:	Marek Suchánek <msuchane>
Priority:	unspecified
Version:	7.6	CC:	awalsh, bgurney, corwin, jbrassow, msuchane, pasik, rbednar, slevine
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-12 19:19:55 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description michal novacek 2019-01-09 12:38:48 UTC

Description of problem:
I have a setup with iscsi multipathed device as a underlying block device for vdo. After reboot however vdo.service is started before this device exists resulting in unavailable vdo device. vdo.service should not start until iscsi have started if vdo underlying device is multipath + iscsi (multipath starts before iscsi).

Version-Release number of selected component (if applicable):
vdo-6.1.1.125-3.el7.x86_64

How reproducible: always


Steps to Reproduce:
1. configure vdo on top of multipath iscsi block device
2. reboot system

Actual results: vdo device not available after reboot

Expected results: vdo device started after reboot

Additional info: 
This issue can be worked around by overriding vdo.service requirements: 
https://github.com/dm-vdo/vdo/issues/9#issuecomment-452644976

Comment 2 Bryan Gurney 2019-01-09 13:36:08 UTC

Updating the title to emphasize that this is when using an iscsi backing device.

Here's the text from the github issue, relevant to systemd sequencing:

(default settings)
"multipathd.service" says "After=iscsi.service"
"iscsi.service" says "Before=remote-fs-pre.target"

(modification made to allow the VDO volume to start automatically)
$ cat /etc/systemd/system/vdo.service.d/override.conf`
[Unit]
After=remote-fs-pre.target multipathd.service

Comment 9 Jakub Krysl 2019-10-15 14:38:54 UTC

Mass migration to Filip.

Comment 11 corwin 2020-05-12 19:19:55 UTC


*** This bug has been marked as a duplicate of bug 1706154 ***

Comment 13 Red Hat Bugzilla 2023-09-15 00:15:05 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days