For resize/cold-migration it's possible that instance
already changed host to destination, but no confirm/revert
has happened yet. In that case resource tracked starts spamming
errors, because it's impossible to match migration and instance.
It's safe to lower log level to debug in that case.
Reviewed: https:/ /review. openstack. org/382195 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=f085fbd7d3b fdf016a37ccc7e6 e28786425f0e4e
Committed: https:/
Submitter: Jenkins
Branch: master
commit f085fbd7d3bfdf0 16a37ccc7e6e287 86425f0e4e
Author: Timofey Durakov <email address hidden>
Date: Tue Oct 4 16:42:09 2016 +0300
Change log level to debug for migrations pairing
For resize/ cold-migration it's possible that instance
already changed host to destination, but no confirm/revert
has happened yet. In that case resource tracked starts spamming
errors, because it's impossible to match migration and instance.
It's safe to lower log level to debug in that case.
Change-Id: I70cb7426e0e284 9ee7d01205ce7b2 d883a126d66
Closes-Bug: #1555320