Apparently fix for this bug https://bugs.launchpad.net/fuel/+bug/1258347
turned out to be non-working anyway.
The reason was that 'lvm_meta_pool' sometimes has non-zero size.
Due to its non-zero size the disk wasn't skipped from partitioning,
thus creating a bunch of partitions even on unallocated drives.
Change-Id: Ifaf8cb6a1f9d5010998b89445c3e575f3957411b
Closes-Bug: #1566399
(cherry picked from commit 825468cb3bb1eb1e6a5e7cd665d89496998cdb54)
Reviewed: https:/ /review. openstack. org/310815 /git.openstack. org/cgit/ openstack/ fuel-agent/ commit/ ?id=6e89fb83e44 a7cd3b286308b66 1f645378576d19
Committed: https:/
Submitter: Jenkins
Branch: stable/mitaka
commit 6e89fb83e44a7cd 3b286308b661f64 5378576d19
Author: Alexander Gordeev <email address hidden>
Date: Wed Apr 27 14:21:42 2016 +0300
Enable unallocated drives back
Apparently fix for this bug /bugs.launchpad .net/fuel/ +bug/1258347
https:/
turned out to be non-working anyway.
The reason was that 'lvm_meta_pool' sometimes has non-zero size.
Due to its non-zero size the disk wasn't skipped from partitioning,
thus creating a bunch of partitions even on unallocated drives.
Change-Id: Ifaf8cb6a1f9d50 10998b89445c3e5 75f3957411b e6a5e7cd665d894 96998cdb54)
Closes-Bug: #1566399
(cherry picked from commit 825468cb3bb1eb1