I think not service tokens here. It's a charmed install but I can't find any evidence of the charms enabling service tokens. I have the keystone expiry set rather long (10800s), if I remember due to migration timeouts some time back.
It seems that restarting the compute service on the source host has resolved the data inconsistency.
Thanks for suggesting.
I think not service tokens here. It's a charmed install but I can't find any evidence of the charms enabling service tokens. I have the keystone expiry set rather long (10800s), if I remember due to migration timeouts some time back.
It seems that restarting the compute service on the source host has resolved the data inconsistency.