With change I6827137f35c0cb4f9fc4c6f753d9a035326ed01b in
Ocata, we changed the ComputeManager to manage a single
ResourceTracker and that single ResourceTracker will
manage multiple compute nodes. The only time a single
nova-compute service hosts multiple compute nodes is for
ironic where there is a compute node per instance. The
problem is the ResourceTracker.stats variable, unlike the
ResourceTracker.compute_nodes variable, is not node-specific
so it's possible for node stats to leak across nodes based
on how the stats are used (and copied).
This change adds a functional recreate test to show the issue
before it's fixed. The fixture setup had to be tweaked a
bit to avoid modifying class variables by reference between
test cases.
Reviewed: https:/ /review. openstack. org/587614 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=fc05626d435 71733da0803df0f d9a7c69766b8fd
Committed: https:/
Submitter: Zuul
Branch: master
commit fc05626d4357173 3da0803df0fd9a7 c69766b8fd
Author: Matt Riedemann <email address hidden>
Date: Tue Jul 31 16:00:28 2018 -0400
Add recreate test for RT.stats bug 1784705
With change I6827137f35c0cb 4f9fc4c6f753d9a 035326ed01b in .stats variable, unlike the cker.compute_ nodes variable, is not node-specific
Ocata, we changed the ComputeManager to manage a single
ResourceTracker and that single ResourceTracker will
manage multiple compute nodes. The only time a single
nova-compute service hosts multiple compute nodes is for
ironic where there is a compute node per instance. The
problem is the ResourceTracker
ResourceTra
so it's possible for node stats to leak across nodes based
on how the stats are used (and copied).
This change adds a functional recreate test to show the issue
before it's fixed. The fixture setup had to be tweaked a
bit to avoid modifying class variables by reference between
test cases.
Change-Id: Icc5f615baa1042 347ec1699eb84ba 0670445b995
Related-Bug: #1784705