Status: New
Owner: ----
New issue 1187 by drew.h...@gmail.com: Disk space check with multiple VGs
is broken
https://code.google.com/p/ganeti/issues/detail?id=1187
What software version are you running? Please provide the output of "gnt-
cluster --version", "gnt-cluster version", and "hspace --version".
gnt-cluster (ganeti 2.15.2-1~bpo8+1) 2.15.2
Software version: 2.15.2
Internode protocol: 2150000
Configuration format: 2150000
OS api version: 20
Export interface: 0
VCS version: (ganeti) version 2.15.2-1~bpo8+1
hspace (ganeti) version 2.15.2-1~bpo8+1
compiled with ghc 7.6
running on linux x86_64
What distribution are you using?
Debian Jessie (ganeti from jessie-backports)
What steps will reproduce the problem?
1. Create an additional volume group whose free space is larger than the
cluster-managed volume group
2. Using the "plain" disk template, attempt to create an instance with a
secondary disk, allocated from the additional (non-cluster-managed) volume
group, whose size is less than the free space in the additional volume
group, but greater than the free space available in the cluster-managed
volume group.
What is the expected output? What do you see instead?
The instance should be successfully created with 2 new disks, but instead
the creation fails with the message:
Can't compute nodes using iallocator 'hail': Request failed: Group default
(preferred): No valid allocation solutions, failure reasons: FailDisk: 1
Please provide any additional information below.
You can create an instance with a secondary disk whose size is equal to
(main_vg_free - primary_disk_size), where main_vg_free is the free space
available in the cluster-managed volume group, and primary_disk_size is the
size of the instance's primary disk that is allocated from the
cluster-managed volume group.
I poked around in the code and it appears this is due to the instance
creation code calling LookupSpaceInfoByStorageType in utils/storage.py. The
comments for that function state explicitly that the function is not
intended to be called in "ambiguous" situations where there are multiple
units of the queried storage type.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
