new hypervisor should appear with available resources set to 0
Bug #1567434 reported by
Vasyl Saienko
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Expired
|
Medium
|
Unassigned |
Bug Description
If Nova tries to check resources on newly added ironic hypervisor during instance spawning, where resources are not updated yet, instance build failed with the following error:
http://
http://
The following operation is failed, since free_disk_space = None.
self.free_disk_mb = compute.
It was reproduced on Liberty nova code.
description: | updated |
tags: | added: ironic |
Changed in nova: | |
assignee: | nobody → Sarafraj Singh (sarafraj-singh) |
Changed in nova: | |
status: | New → Incomplete |
status: | Incomplete → New |
Changed in nova: | |
status: | New → Incomplete |
summary: |
- new hypervisor should apper with available resources set to 0 + new hypervisor should appear with available resources set to 0 |
Changed in nova: | |
assignee: | Sarafraj Singh (sarafraj-singh) → nobody |
Changed in nova: | |
importance: | Undecided → Medium |
To post a comment you must log in.
So, the nova-compute ResourceTracker is updating this field and persisting it in DB (so that the scheduler can get it) in 3 cases :
- when the ResourceTracker (there is one per node) is initiated
- everytime a new instance is claimed for that node
- every 60 secs
What is strange is that the scheduler is getting the list of compute nodes when a request comes in, but that list is created by each ResourceTracker, which means that the RT wouldn't run update_ available_ resources.
Could you please provide us both the nova-compute logs and the nova-scheduler logs at the same time so we could verify if free_disk_gb is set ?