It appears that any related objects such as Networks, Interfaces, Circuits are not correctly invalidating the list view cache on update.
For example, when a network object is changed, ie, parent is updated or addresses are changed, attributes change, etc., any related objects such as Interfaces (to whom these networks might be assigned) do not refresh the new state of the network object automatically.
The cache on an interface object continues to cache the older state of that Network object and this leads to inconsistencies.
We need to investigate why the caching is getting out of phase, and perhaps implement some sort of signal from to invalidate the cache for any related object once a .save() is made.
It appears that any related objects such as Networks, Interfaces, Circuits are not correctly invalidating the list view cache on update.
For example, when a network object is changed, ie, parent is updated or addresses are changed, attributes change, etc., any related objects such as Interfaces (to whom these networks might be assigned) do not refresh the new state of the network object automatically.
The cache on an interface object continues to cache the older state of that Network object and this leads to inconsistencies.
We need to investigate why the caching is getting out of phase, and perhaps implement some sort of signal from to invalidate the cache for any related object once a
.save()is made.