yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #57453
[Bug 1630658] [NEW] nova-scheduler fails when running out of disk space
Public bug reported:
Description
===========
When trying to launch an instance and nova determines that a compute
node is out of disk space, other hypervisors are not considered for
scheduling.
Steps to reproduce
==================
OpenStack deployed using local storage on two nodes (using Kolla), 50 GB disk in my lab.
Launch instances until disk is near full, fex 2 Centos with flavor with 20 GB disk.
Launch another instance with flavor 20 GB disk.
Expected Result
===============
Nova schedules the "other instance" on the second compute host where there are sufficient resources.
Actual Result
=============
Nova fails with "Not Enough Hosts"
[req-a822f4c7-1788-4ff3-b03f-91db6d722937
ec4d0ac3f3684b1db4fa82449091339a df00326cc81048c28466529f82f4cf1a - - -]
Filtering removed all hosts for the request with instance ID
'fb1ee3fe-3230-4d3a-a6d2-7b4a5bae1c09'. Filter results: ['RetryFilter:
(start: 4, end: 4)', 'AvailabilityZoneFilter: (start: 4, end: 4)',
'RamFilter: (start: 4, end: 4)', 'DiskFilter: (start: 4, end: 2)',
'ComputeFilter: (start: 2, end: 0)']\n",
Environment
===========
OpenStack Version: mitaka, installed from Kolla stable/mitaka
Hypervisor: KVM Linux 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57
UTC 2015 GNU/Linux
Storage: Local
Networking: Neutron
** Affects: nova
Importance: Undecided
Status: New
** Attachment added: "Logs"
https://bugs.launchpad.net/bugs/1630658/+attachment/4755206/+files/Logs
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1630658
Title:
nova-scheduler fails when running out of disk space
Status in OpenStack Compute (nova):
New
Bug description:
Description
===========
When trying to launch an instance and nova determines that a compute
node is out of disk space, other hypervisors are not considered for
scheduling.
Steps to reproduce
==================
OpenStack deployed using local storage on two nodes (using Kolla), 50 GB disk in my lab.
Launch instances until disk is near full, fex 2 Centos with flavor with 20 GB disk.
Launch another instance with flavor 20 GB disk.
Expected Result
===============
Nova schedules the "other instance" on the second compute host where there are sufficient resources.
Actual Result
=============
Nova fails with "Not Enough Hosts"
[req-a822f4c7-1788-4ff3-b03f-91db6d722937
ec4d0ac3f3684b1db4fa82449091339a df00326cc81048c28466529f82f4cf1a - -
-] Filtering removed all hosts for the request with instance ID
'fb1ee3fe-3230-4d3a-a6d2-7b4a5bae1c09'. Filter results: ['RetryFilter:
(start: 4, end: 4)', 'AvailabilityZoneFilter: (start: 4, end: 4)',
'RamFilter: (start: 4, end: 4)', 'DiskFilter: (start: 4, end: 2)',
'ComputeFilter: (start: 2, end: 0)']\n",
Environment
===========
OpenStack Version: mitaka, installed from Kolla stable/mitaka
Hypervisor: KVM Linux 3.10.0-327.el7.x86_64 #1 SMP Thu Nov 19 22:10:57
UTC 2015 GNU/Linux
Storage: Local
Networking: Neutron
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1630658/+subscriptions
Follow ups