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 ?
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 ?