RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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

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

Mass migration to Filip.

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

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