Julia Kreger e1d457da36 Ignored error state cache for new requests ... A possibility exists where inspector *can* fail upon inspection if the database connectivity was lost on a prior action. This is because the last database transport is potentially bad and fails upon load for the transaction. The cache can then end up with an "error" state entry, which upon retrying can fail becasue it is already in error state Because there really are no guarentees regarding database failures, the best thing to do is to not trust the prior cache state if it is in error and to reset it to starting upon new introspection requests. This prevents operators from *having* to perform process restarts to force all loads to be from the database unless they manage to have a multi-inspector cluster and get another inspector node to inspect in the mean time. Change-Id: I04ae1d54028862642d043f3a8f3af99405863325 Story: 2008344 Task: 41246 Related: rhbz#1947147 (cherry picked from commit d972dc93cd)		2021-10-04 18:04:04 +00:00
..
notes	Ignored error state cache for new requests	2021-10-04 18:04:04 +00:00
source	Add release version to release notes	2020-07-07 18:48:23 +02:00