Open Stack

On 11/4/2018 4:22 AM, Mohammed Naser wrote:
> Just for information sake, a clean state cloud which had no reported issues
> over maybe a period of 2-3 months already has 4 allocations which are
> incorrect and 12 allocations pointing to the wrong resource provider, so I
> think this comes does to committing to either "self-healing" to fix those
> issues or not.

Is this running Rocky or an older release?

Have you dug into any of the operations around these instances to 
determine what might have gone wrong? For example, was a live migration 
performed recently on these instances and if so, did it fail? How about 
evacuations (rebuild from a down host).

By "4 allocations which are incorrect" I assume that means they are 
pointing at the correct compute node resource provider but the values 
for allocated VCPU, MEMORY_MB and DISK_GB is wrong? If so, how do the 
allocations align with old/new flavors used to resize the instance? Did 
the resize fail?

Are there mixed compute versions at all, i.e. are you moving instances 
around during a rolling upgrade?

-- 

Thanks,

Matt