Comment 4 for bug 1528743

Is this still an issue now that we've been doing resource claims for DISK_GB, VCPU and MEMORY_MB (via the FilterScheduler and placement) since Pike? It could still be an issue for the CachingScheduler, but out of date information is kind of a known limitation when using the CachingScheduler.

Also, I still don't really understand the issue. You're saying the compute node record isn't getting updated because nothing changed, so then why do we need to update the host state information in the scheduler for that host if nothing changed on it?