Unexpected stale read warning-level messages in Front50 logs

Issue

Warning-level log messages may appear in a user's Front50 logs that look something along the lines of:

| 2021-10-14 15:23:23.548 WARN 1 --- [pool-6-thread-3] c.n.s.f.m.s.DefaultServiceAccountDAO : Unexpected stale read for 9135a6cb-d088-4cde-82c2-bfc354d4abfd@managed-service-account (current: Mo | This may also manifest in the form of applications, pipelines, notifications or execution history not loading at all, or displaying incorrectly in the Spinnaker UI.

Cause

Since Front50 stores and serves metadata out of an in-memory cache, there may have been or currently is an outage with the currently configured object store. This may also occur after migrating the Spinnaker instance to another (for example, a Disaster Recovery) location, but not moving Operator's object store configuration to the replicated object store.