If server crash or reboot happened, LIO target configuration
will be initialized after boot up a server. Currently, Cinder
has a functionality to save LIO target configuration to save
file at several checkpoint.
If LIO target service is configured properly, LIO target
configuration is restored by this service during boot up
a server, but if not, existing in-use volumes would become
inconsistent status after c-vol service starts.
If there is no iSCSI target configuration during
ensure_export, LIO dirver should restore the saved
configuration file to avoid the problem.
Closes-Bug: #1536248
Change-Id: I74d300ba26a08b6f423f5ed3e13495b73cfbbd52
(cherry picked from commit 5cec4056eb061004b400c1dc5b946bf890b4bab0)
Reviewed: https:/ /review. openstack. org/283085 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=f5ec1be2d8b decb0b94bfb298b 03bb1e49ee8cc4
Committed: https:/
Submitter: Jenkins
Branch: stable/liberty
commit f5ec1be2d8bdecb 0b94bfb298b03bb 1e49ee8cc4
Author: Mitsuhiro Tanino <email address hidden>
Date: Fri Jan 22 11:31:25 2016 -0500
[LVM] Restore target config during ensure_export
If server crash or reboot happened, LIO target configuration
will be initialized after boot up a server. Currently, Cinder
has a functionality to save LIO target configuration to save
file at several checkpoint.
If LIO target service is configured properly, LIO target
configuration is restored by this service during boot up
a server, but if not, existing in-use volumes would become
inconsistent status after c-vol service starts.
If there is no iSCSI target configuration during
ensure_export, LIO dirver should restore the saved
configuration file to avoid the problem.
Closes-Bug: #1536248 6f423f5ed3e1349 5b73cfbbd52 4b400c1dc5b946b f890b4bab0)
Change-Id: I74d300ba26a08b
(cherry picked from commit 5cec4056eb06100