NULL free_disk_gb causes scheduler failure
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
aginwala |
Bug Description
It appears a race exists between nova-scheduler and the compute manager when a ComputeNode entry is created for the first time.
The following log messages were noticed after multiple transient failures to create VM on a newly deployed single node system.
2015-11-03 18:41:27.886 13735 WARNING nova.scheduler.
2015-11-03 18:41:27.904 13783 WARNING nova.scheduler.
Traceback (most recent call last):
File "/usr/lib/
executor_callback))
File "/usr/lib/
executor_callback)
File "/usr/lib/
result = func(ctxt, **new_args)
File "/usr/lib/
return func(*args, **kwargs)
File "/usr/lib/
filter_properties)
File "/usr/lib/
filter_properties)
File "/usr/lib/
hosts = self._get_
File "/usr/lib/
return self.host_
File "/usr/lib/
host_state = self.host_
File "/usr/lib/
return HostState(host, node, **kwargs)
File "/usr/lib/
self.update_
File "/usr/lib/
free_disk_mb = free_gb * 1024
TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'
2015-11-03 18:41:27.907 13783 WARNING nova.scheduler.
I believe that during the execution of resource_
Commit 6aa36ab seems likely to have exposed this more widely.
Versions (Kilo):
ii nova-common 1:2015.
ii nova-compute 1:2015.
ii nova-compute-kvm 1:2015.
ii nova-compute-
ii python-nova 1:2015.
ii python-novaclient 1:2.22.
tags: | added: scheduler |
Changed in nova: | |
status: | New → Confirmed |
assignee: | nobody → aginwala (aginwala-f) |
importance: | Undecided → Medium |
Changed in nova: | |
importance: | Medium → Low |
Changed in nova: | |
milestone: | none → ongoing |
Is it Kilo or Juno?