Bug 1522906

Summary: vdo volumes should persist across reboot
Product: Red Hat Enterprise Linux 7 Reporter: Louis Imershein <limershe>
Component: vdoAssignee: Joseph Chapman <jochapma>
Status: CLOSED ERRATA QA Contact: Jakub Krysl <jkrysl>
Severity: high Docs Contact:
Priority: unspecified    
Version: 7.5CC: awalsh, jkrysl, sweettea
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: 6.1.0.89 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 15:49:25 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 Louis Imershein 2017-12-06 17:30:49 UTC
Currently, you have to manually install an systemd script to allow the vdo module to persist across reboots

Comment 2 Andy Walsh 2017-12-06 20:53:36 UTC
The RPM should enable the service at install.  So inside the %install section, we should be performing a 'systemctl enable vdo.service'

Comment 3 Andy Walsh 2017-12-07 13:54:32 UTC
Moving this to the correct component.  The systemd unit is in the user-space RPM, not the kernel-mode RPM.

Comment 6 Jakub Krysl 2017-12-14 12:03:25 UTC
Created vdo, rebooted, checked vdo. Created vdo is still there, verified.

Comment 9 errata-xmlrpc 2018-04-10 15:49:25 UTC
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-2018:0871