Reviewed: https://review.openstack.org/597553 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=9c842d1aa68d67383114f783c946492282832e5b Submitter: Zuul Branch: master
commit 9c842d1aa68d67383114f783c946492282832e5b Author: Matt Riedemann <email address hidden> Date: Wed Aug 29 10:41:25 2018 -0400
Log the operation when updating generation in ProviderTree
Today when a provider generation is updated we get a mostly unhelpful message in the logs like:
Updating resource provider bc0f4c8e-96e2-4e68-a06e-f7e0ac9aac6b generation from 0 to 1
What we really want to know with that is in what context did the generation change, i.e. did inventory or traits change?
This adds the actual operation to the log message when generation changes.
Change-Id: I9b61f1dfb8db06e02ff79e19c055c673094a4ed2 Related-Bug: #1789654
Reviewed: https:/ /review. openstack. org/597553 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=9c842d1aa68 d67383114f783c9 46492282832e5b
Committed: https:/
Submitter: Zuul
Branch: master
commit 9c842d1aa68d673 83114f783c94649 2282832e5b
Author: Matt Riedemann <email address hidden>
Date: Wed Aug 29 10:41:25 2018 -0400
Log the operation when updating generation in ProviderTree
Today when a provider generation is updated we get a mostly
unhelpful message in the logs like:
Updating resource provider bc0f4c8e- 96e2-4e68- a06e-f7e0ac9aac 6b
generation from 0 to 1
What we really want to know with that is in what context did the
generation change, i.e. did inventory or traits change?
This adds the actual operation to the log message when generation
changes.
Change-Id: I9b61f1dfb8db06 e02ff79e19c055c 673094a4ed2
Related-Bug: #1789654