Comment 5 for bug 1630658

Revision history for this message
Magnus Lööf (magnus-loof) wrote :

Sorry guys. I edited the "hypervisor" list because I had two more Hyper-V hosts that were not part of the equeation, in an effort to simplify the problem description. Bad move.

Anyway. I believe the logs show the following:

1. There are - at least ;-) - two hypervisors with sufficient disk space:

   openstack hypervisor show 3:
   vcpus_used 0
   free_disk_gb 49

   openstack hypervisor show 5:
   vcpus_used 0
   free_disk_gb 49

2. It is possible to schedule servers to both hypervisors:

   7 x nova boot --image cirros --flavor m1.tiny

   openstack hypervisor show 3:
   vcpus_used 5
   free_disk_gb 45

   openstack hypervisor show 5:
   vcpus_used 3
   free_disk_gb 46

3. There is diskspace remaining on control02 (id 5) after trying to schedule:

   nova boot --image CentOS-7-x86_64-GenericCloud-1608.qcow2 --flavor m1.small three

   openstack hypervisor show 5:
   vcpus_used 0
   free_disk_gb 49

4. Nova fails to schedule, even though there is sufficient disk on control02 (id 5):

  'DiskFilter: (start: 4, end: 2)'

  The DiskFilter *should* have returned '3' (both Hyper-V hosts also had sufficient disk + control02)