The only way to reliably determine whether we are using a legacy
(pre-Grizzly) backing structure is to look at the backing file
reference for the instance/disk itself. Thus, if we determine the
backing file contains an underscore, we use the value following it
as our legacy_backing_size, which is then used to create the
necessary backing file.
Reviewed: https:/ /review. openstack. org/32767 github. com/openstack/ nova/commit/ 69dd7c50a955187 88018dd1cb8aad6 0029fdac42
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit 69dd7c50a955187 88018dd1cb8aad6 0029fdac42
Author: Rafi Khardalian <email address hidden>
Date: Wed May 29 21:26:19 2013 +0000
Regenerate missing resized backing files
Fixes bug 1185588 (for stable/grizzly)
The only way to reliably determine whether we are using a legacy backing_ size, which is then used to create the
(pre-Grizzly) backing structure is to look at the backing file
reference for the instance/disk itself. Thus, if we determine the
backing file contains an underscore, we use the value following it
as our legacy_
necessary backing file.
Change-Id: I145f71068c972a 604e5361ae79d63 15286136786 fee90e41aa5c40a f780d3e04a
Cherry-Pick: 6e768363450774c